waiting
What waits for her yes. What waits for her yes, read only, each whole. Her yes is her own tap in her office or phone: say what it is, never ask its question again.
Where it is
In the road area (her next step, her taps, coaching moments, her programme, immersives, her review, what waits for her yes, what was made, and her office as her phone reads it): open it with tools_for { area: "road" }, then call it with read_tool { name: "waiting", args }.
Does it need a yes?
Reads only: it changes nothing. Here: what waits for her yes, read only (her yes is her own tap).
Inputs
| Input | Type | Needed | About |
|---|---|---|---|
run_id | string | no | The run_id from start. Pass it on every call: it keeps your task held. · 1 to 100 characters |
Example
{
"name": "waiting",
"arguments": {}
}When it is refused
invalid: The input isn't right. The sentence names the field and the fix; nothing was done. Fix it and call again.not_found: No such thing in this company (a task, file, person, record). Check the number or name, or list first.not_allowed: Not without another step: the owner's yes, your own task held with pick_up, or a setting the owner turns on. The sentence says which.taken: Someone else holds it (another AI on that task). Pick another task.stale: It changed since you read it. Read it again and use the new version.failed: On our side or a service's, never your input. Try again in a minute; if it keeps failing, call report_problem.