Monitoring Runs
Track run progress and status from the Bluebricks app or CLI
Overview
Every run progresses through a series of statuses as it moves from planning to completion. You can monitor run progress in real time from the Bluebricks app or list environments from the CLI.
For background on how runs work, see Runs. For details on the plan-approve-apply lifecycle, see the plan phase and apply phase sections on that page.
Run statuses
Pending
Run is queued and waiting to start
Planning
Generating the execution plan across all packages
Waiting for input
Plan complete, awaiting approval
Plan approved
Approved, pending installation
Installing
Actively provisioning or updating infrastructure resources
Completed
Run finished successfully
No changes
Plan detected no infrastructure changes
Failed
Run encountered an error
Canceled
Run was canceled before completion
Skipped
Run execution was skipped
Drifted
Infrastructure differs from planned state (drift detection only)
How to monitor runs in the Bluebricks app
Environments list
Navigate to Environments to see the latest run status for each environment. Each row shows a status badge with the current stage.
Run detail page
Click an environment to open its run detail page. The detail page shows:
Status timeline: a vertical progression through each stage with timestamps for every transition
Plan diff: resources to create, update, or destroy, grouped by package
Live logs: real-time streaming logs during execution, filterable by log level
Resource list: individual resource states, configuration, and outputs
Dependency graph: visual representation of resource dependencies
Approving or rejecting a run
When a run reaches Waiting for input status:
Click Approve & Apply to proceed with the plan (keyboard shortcut:
Cmd+Enter/Ctrl+Enter)Click Reject to cancel the run (keyboard shortcut:
Cmd+Z/Ctrl+Z)
If you reject a run that is already partially applied, some resources may have been modified. Review the run logs to understand what was applied before the rejection.
For uninstall runs, the Approve & Apply button appears in red. A confirmation dialog reminds you that approving will remove all previously provisioned resources.
If the collection has a cost quota configured and the run would exceed it, the Approve & Apply button is disabled. Contact the collection owner to adjust the quota or approve the run.
How to monitor runs via the CLI
List environments
Output columns:
SLUG: environment identifier
BLUEPRINT: blueprint name and version
TARGET ENVIRONMENT: target collection name
Limit results
The default limit is 100. The CLI paginates results and prompts to fetch more if available.
For the full command reference, see bricks deploy list.
See also
Runs: run lifecycle and plan/apply phases
Destroying Environments: uninstall environments and clean up resources
Creating Environments: deploy blueprints into collections
Last updated
Was this helpful?