Skip to content

Change and run states

Badge names below are generated from the console’s own badge definitions, so they always match what you see. Meanings are the descriptions the change page shows under its header.

Badge Value Meaning
Clarifying clarification Clarifying request
Criteria needed criteria_pending Success criteria need confirmation
Ready to plan ready_for_plan Ready to plan
Planning planning AI is preparing the next step
Plan review plan_ready Exact plan needs a Developer decision
Approved approved Plan approved; implementation can start
Implementing implementing Implementation is running
Reviewing reviewing Independent review is running
Pull request ready pull_request_open Locally tested pull request is ready
Needs attention failed Workflow needs attention
Cancelled cancelled Request cancelled

Two overrides apply on a change page: while the execution is brokering, the badge reads Pull request delivery; while a cancellation is pending, it reads Cancellation requested. The Changes list groups states as Needs attention (Criteria needed, Plan review, Approved, Needs attention), In progress (Planning, Implementing, Reviewing), and PR ready.

Badge Value
Queued queued
Implementing implementing
Reviewing reviewing
Pull request delivery brokering
Pull request ready pull_request_open
Failed failed
Cancelled cancelled

Jobs: Waiting, Queued, Running, Succeeded, Failed, Cancelled. Workflows:

Queued, Running, Succeeded, Failed, Cancelled. Stages shown on a run are Implementation, Independent review, and Connection test.

Dimension Values
Registration Awaiting deployment, Registered, Self registered
Control state Active, Draining, Disabled, Revoked
Reported status Online, Needs attention, Offline
Authentication Authentication unknown, Authenticated, Unauthenticated, Authentication failed

A planned runner shows Awaiting deployment in place of its reported status. The fleet row also shows a readiness stage: Registration plan ready, Disabled or Revoked, Draining, Provider login required, Ready for jobs, Health check needs attention, or Offline.

Runner ready, No matching runner.

Badge Value
Ready ready
Approved approved
Executing executing
Succeeded succeeded
Failed failed
Cancelled cancelled
Expired expired
Superseded superseded
Reconciliation required reconciliation_required
Badge Value
Queued queued
Running running
Succeeded succeeded
Failed failed
Cancelled cancelled
Outcome unknown outcome_unknown
Reconciliation required reconciliation_required
Reconciled reconciled

Deployment runners, connections, environments

Section titled “Deployment runners, connections, environments”
  • Runners: reported status Online, Needs attention, Offline; registration Planned, Registered; control Active, Draining, Disabled, Revoked.
  • Connections: Pending, Ready, Error, Disabled.
  • Environments: Active, Paused, Archived.
  • Adapters: Available, Catalog.
  • Connection status: Needs credentials, Not synchronized, Connected, Needs attention, Disabled.
  • Sync run: Sync queued, Sync running, Sync retrying, Sync succeeded, Sync failed.
  • Service lifecycle: Draft, Active, Paused, Disconnected, Archived. Unenrolled candidates show Available, Access lost, or Repository archived.
  • Pull-request delivery: PR delivery enabled, PR delivery disabled, plus Not configured and Credential missing before a bot exists; credential Credential not checked, Credential verified, Credential failed.
  • Invitation email: Email queued, Emailed, Email failed, Email cancelled.

Outcome: Succeeded, Denied, Failed, Pending. Severity: Info, Warning, Error, Critical.

Complete, Next step, Not started, Last known, Could not check.