Tracking Runs

Every workflow execution has a run details page at /self-service/runs/<run-id>, reachable from Recent runs, from the Deployments catalog page (Run link column), or from the redirect after you execute a workflow.

Anatomy of the page

Section	What it shows
Header	workflow name, run id (r_...), overall status badge, and Cancel run while in progress
Status cards	current status, total duration, related entity, summary
Step graph	the workflow DAG — each node shows its type (GITHUB, GITLAB, APPROVAL, UPSERT_ENTITY), live status (PENDING, IN PROGRESS, SUCCESS, FAILURE, SKIPPED), a one-line result, and an open link to the external run/pipeline where applicable
Logs	timestamped log of the whole run; filter to a single step with the All steps dropdown

Step statuses

• PENDING — waiting for its dependencies.
• IN PROGRESS — dispatched and running (or waiting for approval).
• SUCCESS / FAILURE — final result, propagated from the external system (Actions run conclusion, pipeline status, approval decision).
• SKIPPED — a dependency failed and the step's condition was ON_SUCCESS.

Timeouts and cancellation

• Each step has a timeout (10 minutes for the demo's deploy steps). A step that exceeds it is failed, and the run proceeds according to conditions.
• Cancel run stops dispatching new steps. Already-running external pipelines finish on their side but no longer affect the run.

Where results land

Steps of type UPSERT_ENTITY write to the catalog. In the demo, every run — success or failure — becomes a row on the Deployments page with a Run link back to the run details, so the catalog is the long-term deployment history:

Next: browsing the catalog →