Part

Run state

You might say: run status, queued, in progress, completed

The durable state record for one run from dispatch through completion.

What it does

Lets the orchestrator show capacity, decide which transitions are legal, and trigger the next task from a known outcome.

Ask

Is this run queued, in progress, or finished, and what conclusion or failure explains the state?

Typical

Queued, requested, waiting, in progress, completed, cancelled, failure, skipped, stale, success, or timed out.

Trouble

A run stays queued forever, finishes without a conclusion, or a retry looks like a new piece of work.

What to look for

1. Queued, in progress, and completed status pills
2. Start and finish timestamps
3. A conclusion such as success, failure, cancelled, or timed out

Connections

• See also: Try cap
• See also: Trigger

Sources

1. GitHub, REST API endpoints for workflow runs, List workflow runs for a repositoryCan be one of: `completed`, `action_required`, `cancelled`, `failure`, `neutral`, `skipped`, `stale`, `success`, `timed_out`, `in_progress`, `queued`, `requested`, `waiting`, `pending`
2. GitHub, REST API endpoints for workflow runs, About workflow runs in GitHub ActionsYou can use the REST API to view, re-run, cancel, and view logs for workflow runs.

Use it on your project

teardown-apply: hold "Run state" (run-state) from the teardown at https://teardownatlas.com/software-factory/ against my project

Paste it into a coding agent that has the teardown skills.

An AI agent wrote this map with the teardown skill. It can contain errors: check the sources before you rely on a part. About and legal