Item statuses

A work item carries a single status describing where it is in its lifecycle. This page defines the five item statuses, what each means, how they transition, and where you see them. These are distinct from flow run statuses — an item status describes a unit of work, not a flow execution.

See Items for the API and Item status reporting for the UI.

The five item statuses

Known transitions

Code
IN_PROGRESS ──▶ REVIEW ──▶ IN_PROGRESS ──▶ COMPLETE
                                     └────▶ FAILED

• An item starts IN_PROGRESS as the Agent processes it.
• A Review node routes the item to REVIEW. Submitting the review returns it to IN_PROGRESS.
• Marking an item complete (the Complete action) sets it to the terminal COMPLETE status.
• An item that errors becomes FAILED. An item can also end as CANCELED.

Terminal statuses (COMPLETE, FAILED, CANCELED) are fixed once reached; IN_PROGRESS and REVIEW are non-terminal.

Status reporting cards

The Items list shows a live count above it, one card each for In Progress, Review, Complete, and Failed. Canceled items aren't shown as a card. See Item status reporting.

Where you can see item statuses

• Items list — each item shows a Status badge, and you can filter the list by one or more statuses. See Human review.
• API — the status field on ItemResponse, and the status filter on GET /items (which accepts one or more values, e.g. status=REVIEW&status=FAILED). See Items.

Where to go next

• Items — the API resource, where status is returned and filtered.
• Item status reporting — the reporting cards and what they summarize.
• Human review — work items in the REVIEW status.
• Flow run statuses — the separate status vocabulary for runs.