Timer on a Wait for me step
- Desktop, mobile and web
- All plans
What it does
A Wait for me step can go on by itself when nobody answers, for the runs you decided in advance do not need you. After the delay the run takes the connection you picked, only if that connection's conditions match the flags reported by the step that led there. Any other run keeps waiting for you with no limit, so the step stays a real gate for anything you did not pre-approve. Off by default.
Where to find it
Teams window, select the Wait for me step, Continue by itself > Take a connection when nobody answers.
How to use it
- Draw the connections out of the step, for example
routine = truetowards Deploy androutine = falseback to Dev. - Turn on Take a connection when nobody answers, enter the minutes and pick the connection, here the
routine = trueone. - Have the step before report that flag when the case is routine. The step is told about the timer and which flags skip you.
While the timer runs, the answer box says Runs by itself at 14:32 and goes to Deploy, unless you answer first, and so does the notification. Keep waiting for me, picking a route or typing in the box stops the timer for that pause: someone answering is never overtaken. Answering works as usual.
When the time comes, the handoff on the timeline reads Auto-answered on timeout after 30 min with the route it took, the run's notes say the same, and the next step is told that nobody looked. No human decision is recorded and no flag is written.
Settings
timeoutMinutes(node field of a Wait for me step, Teams window > the step > Continue by itself; off by default, 1 to 10080 minutes; since 2026-11-04, reported by Robert): the delay. NeedstimeoutEdge.timeoutEdge(same place, the connection picker): the id of one outgoing connection of the step. A connection with no condition lets every run through after the delay, and the editor warns about it.
Agent tools (MCP)
teams_get/teams_save: read and write both fields on an await node (nodePatchesincluded; give the edge anidto name it). A half-set timer is refused. Set them only when the user asked, since they let a run through a human gate. An agent of a live run cannot change them on its own team.backlog_get:run.awaitingUserstill reads true while the timer runs.
Providers
All providers, no difference: the runner decides, not the CLI.
Mobile
Same line, same Keep waiting for me button and same rules on the phone, where typing or picking a route stops the timer too. A run on another computer shows the time, and the answer stays on that computer.
Limits
The timer runs in the desktop app, so nothing moves while the app is closed. At the next launch a passed deadline gets 5 more minutes, shown on the card. With autoLaunchAgentsAtStartup off, a passed deadline drops the timer and the run waits for you, because nothing starts by itself at launch. Editing the team during the pause so the connection or its conditions no longer apply also drops the timer.
Common questions
- What is the difference with Take the recommended option when nobody answers? That setting (
questionAutoAnswerMinutes) covers a step's question cards that the agent marked reversible and offline, across a whole team. This one covers one gate, on a condition you set yourself, and may let a live operation through. - A run did not continue on its own. Why? Its flags did not match the connection, or someone touched the box, or the app was closed. The card says so: no time on it means the run waits for you.
- How do I stop a timer without answering yet? Keep waiting for me. The timer does not come back for that pause.
Related
- Agent Teams: the graph, conditional connections and the answer box.
- Team step entry check: a machine verdict before a step starts instead of a person after it.