workflows-status

Check Archon workflow status by retrieving current, running, and recent runs via REST or by reading the local SQLite state, providing per-run visibility including start time and steps for fast issue diagnosis.

Yes, you can query historical workflow statuses by reading the local archon.db SQLite database directly, which provides comprehensive visibility into recent runs even when the Archon server is not actively running.

Available filters for querying Archon SDLC workflow runs include --running to show live executions, --recent N to limit the number of historical records, and --run-id to target a specific workflow run instance.

No, you do not need Archon on your PATH to monitor workflow run statuses, as this approach retrieves current and recent runs via REST access or by reading the local SQLite state independently.

The default REST endpoint for retrieving Archon workflow status is http://localhost:3090, which allows you to fetch live and recent workflow runs directly from the running Archon server.

Use SQLite state instead of REST for workflow status monitoring when the Archon server is not running, as reading the local archon.db allows you to access historical run data and maintain audit trails without live server connectivity.