Sometimes a run reaches a point it can’t decide on its own — a choice to make, a detail to confirm, an ambiguity to resolve — so it stops and asks you. This page covers answering that question and getting the run moving again. For where this state sits among the others, see Run states.
Confirm the run is waiting for an answer
A run that has paused to ask you something sits in the Waiting for Answer state. Open the run detail page — the status badge near the top reads Waiting for Answer.
Unlike a gate or a payment pause, this state is specific to this run: it stopped because the work in front of it needs a decision only you can make.
Read the question
The run detail page shows a panel telling you the run is waiting for your answer. The question itself appears inside it, in its own box.
Read it carefully before you respond. The question is asked in the run’s own words — it might be asking you to pick between two approaches, confirm an assumption, or fill in a detail the task didn’t specify. Your answer steers the rest of the work, so answer the question that was actually asked.
Type your answer
Below the question is a text box with the placeholder Type your answer…. Write your response there in plain language — full sentences are fine, and so is a short instruction. The box accepts free text only; there are no options to pick from.
There’s no penalty for taking your time. The run holds its place indefinitely while you decide — it won’t time out or move on without you. If you need to check something before answering, leave the page and come back; the question will still be there.
When your answer is ready, select Submit Answer.
The run continues from where it paused
Once you submit, the run reads your answer, leaves Waiting for Answer, returns to Running, and picks up from the step where it stopped. Nothing already done is repeated — your answer simply unblocks the step that was waiting on it.
A short moment passes between submitting and the run restarting. Give it a beat and refresh if the page still shows the old state.
If you submit an answer and realise it was wrong, you can’t take it back — the run has already moved on. Let the run continue; if the result isn’t right, you can cancel it and start a fresh run from the task page.
Answering a question isn’t admin-only — anyone on the project’s team who can open the run can respond.
For every state a run can pass through, and the other ways a run pauses for you, see Run states.