Fix a task whose slot couldn't copy the repository
Before a task runs, its node copies the project's repository into the task's slot, signed in with the git account of the person who started the task. When that copy fails, the task never starts. The node tries again for a while, and the task shows Waiting. If it keeps failing the same way, the task stops and asks you, under the heading Checkout failed, what to do. Nothing runs until you fix the cause and answer.
Who can do this: anyone with edit access to the task's project. Change integration branch also needs permission to edit the project.
- On the board, hover the task's state. Waiting: its worktree could not be prepared., or a sentence about the git service or a git account, means the copy failed. Open the task to read the whole reason, with what the node said. While the task is still Waiting, the node keeps trying.
- If the task now shows Asking, select it. It opens on the Q&A tab, on a question marked Checkout failed. The question says what went wrong, how many times the node tried, and what the node said.
- Fix the cause the question names:
- The person who started the task has no account for the repository on that git service, or the service refused their login: they connect or reconnect it on their profile's Git section. See Your profile.
- Their account can't see the repository: they get access to it, or a teammate who has access starts the task instead.
- The git service could not be reached or did not answer in time: wait until it answers.
- The node's git credential helper is missing: the node's install is broken. Run the node install again; see Add a node.
- The integration branch doesn't exist: go to step 5.
- Pick Retry. The task goes back to the queue, and a node tries to copy the repository again.
- If the branch was the problem, type the right branch name in Note, pick Change integration branch, then select Send. The project switches to that branch for every task, and this one starts again.
- If the task should not run at all, pick Cancel task. It goes back to Draft and nothing retries.
- If the task stays Waiting and its reason ends with Reset the task to retry on a fresh worktree, or says a node can't copy with a login that works on other nodes, open the task's ⋯ menu, select Reset and confirm, then open ⋯ again and select Start. The task takes a new slot, often on another node.
Once the copy works, the task shows Queued, then Running, and its Runner field names the node and the slot.
A task whose starter has no access at all may ask a shorter question instead: your name, that you don't have access to the repository, and Start anyway? Yes runs the task in an empty folder without the code; No sends it back to Draft. To avoid that question, see Start a task when you can't see its repository.
Related
- How worktrees work: what a slot is and who holds it.
- Answer a task's question: the Q&A tab, Note and Send.
- Check on a task that won't start in its slot: when the slot is ready but the run never reports.