Retrying a Linear task that failed at the start uses your own model connection

If the first attempt stopped early, for example because the issue could not be fetched, your reply was treated as a follow-up on a task that had never been set up. That skipped the step that records who started the task, so billing could not find your personal model connection, treated the run as one on the managed key, so it either used the workspace's daily managed task or stopped with a top-up request. The retry now finishes that setup first. Work that really does run on the managed key is billed as before.