Resume an agent run waiting on human input

When an agent reaches a Question step, the run pauses with the status Waiting until someone replies. Reply from the run page, or in the chat the run belongs to, and the run picks up where it stopped. A run that gets no reply for 30 days is ended automatically.

When an agent pauses for input

A run pauses when it reaches a Question step, or when a run started on a schedule or by a trigger is missing input it cannot work without. The run shows as Waiting in Run History, and the run page shows a Waiting for input panel with the question.

Who can reply

The person who started the run can reply, and so can anyone in the chat the run belongs to. Scheduled and triggered runs run as the agent owner, so the owner replies to those.

Reply to a waiting run

1. Open the run from the agent's Run History. The sidebar opens on the waiting step.

2. Read the question in the Waiting for input panel.

3. Type your answer in the reply box. Any non-empty reply is accepted, so answer the question as asked.

4. Click Send reply, or press Cmd+Enter (Ctrl+Enter on Windows).

We record your answer on the run, mark the step as done, and the run continues. To answer in the conversation instead, click Open in chat and reply to the question there.

What happens after you reply

The run continues through its remaining steps. If it reaches another Question step, it pauses again. When the last step finishes and the output is delivered, the run completes. See Agent output contracts and branch-specific outputs.

How long a run can wait

A waiting run stays open for 30 days. If nobody replies in that time, we end the run as Failed with the reason that it timed out waiting for input. To end it sooner, open the run and click Stop run.

Waiting runs also affect when the agent's scheduled runs start. See Agent Triggers.

Why a reply might not go through

What to read next

• Agent Control Steps for setting up Question steps

• Agents Overview for how agents handle branching, outputs, and run states