Get flow status
flow_get_statusCheck a flow's current status: each step, its owner, off-sequence exchanges, and the next tool to call. Always current from recorded exchanges.
Instructions
Where a run has got to: every step with its status and who owes it, any exchanges that arrived off-sequence, and what the loop needs next. State is derived from the recorded exchanges on every call, so this is always current. Name the run by flow_id (or transaction_id once it has one). Read it whenever you lose track; next says exactly which tool to call.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| flow_id | No | The flow started with flow_start. Works before the transaction id exists, so prefer it. | |
| session_id | Yes | Session returned by session_create. | |
| transaction_id | No | A specific transaction. Only known once the flow's first action has crossed the wire. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| seq | Yes | Latest event number. Pass it to flow_await as after_seq. | |
| next | Yes | What the loop needs next, without doing it. | |
| events | No | What has happened in this session since your last call — the participant's callbacks, steps sent automatically, refusals, form submissions. Attached to every session-scoped result and delivered exactly once, so read it here instead of polling. Absent when nothing happened. `more` above zero means call record_get_events for the rest. | |
| attempt | Yes | Which try of this flow the run is on. 1 unless restarted. | |
| flow_id | Yes | ||
| sequence | Yes | The main sequence, in order. | |
| abandoned | No | Set when reading an attempt that flow_restart wrote off. Its record is kept as evidence but it cannot be advanced; the run has moved on. | |
| attention | No | Why auto-advance stopped, if it did. | |
| mock_role | Yes | ||
| extra_steps | Yes | Side-channel steps — unsolicited updates and their replies. | |
| flow_status | Yes | ||
| missed_steps | Yes | Exchanges that did not fit the flow. Compliance findings. | |
| transaction_id | Yes | Null while the flow's first action has not yet crossed. | |
| reference_data_keys | Yes | Form steps with a resolved artefact waiting in business data. |