Ticket states
Use this page to interpret ticket states and the actions offered when execution pauses.
Ticket states
| State | Meaning |
|---|---|
running | Nodes are running. |
paused_budget | A budget threshold was crossed: continue, extend or stop. |
paused_human | A human node, a repeated tool call, or a pause asked by a person. |
needs_human | The engine stopped and hands over: retry, take over or close. |
done | The flow reached END. |
cancelled | Stopped by a person; the artifacts produced so far are kept. |
failed | An error the engine cannot hand over, such as a condition with no edge to take. |
Tickets are numbered T-0001, T-0002…
What the engine asks
Every pause carries the question and the actions it accepts. Actions are English identifiers; interfaces translate them for people.
| Pause | Actions |
|---|---|
| Budget threshold (75% and 90% of any dimension, per agent or per ticket) | continue, extend (+50% of that dimension), stop |
| The same tool call repeated four times in a row | retry, take_over, close |
| Human node | the node's own actions |
Hand-over (needs_human) | retry, take_over, close |
At 100% of a budget the call is refused and the ticket goes to needs_human. A feedback edge past
its maxRounds, or one that sends back the same feedback twice, also hands over. retry then
resets the counters and runs the stopped node again.
A rejection on a human node goes back through the flow when an edge handles it, for example
when: "decision.action == 'reject'" with newRound: true. Otherwise the engine hands over.
In a when, an artifact named with - is written with _: text-request is
text_request.topic, since text-request.topic would read as a subtraction.