Skip to main content
Running an Automation creates a run and one or more actions underneath it. Each action represents work on a specific target, such as a repository or project selected by the trigger configuration. Use this page when you want to start an Automation manually, monitor progress, inspect failures, or review what the agent actually did.

​
What a run contains

  • Run: the top-level execution record
  • Actions: per-target executions created under that run
  • Execution details: action status, step progress, failures, and, when available, the full agent session for an action

​
Start an Automation

Disabled Automations cannot be started. The Run button is hidden and triggers are ignored while an Automation is disabled. Re-enable it first.
  1. Open the Automation (or use the three-dot menu from the list).
  2. Click Run.
  3. Confirm target repositories/projects.
Run Automation

​
Monitor progress

The run details page shows real-time execution status. Execution status Action statuses:
  • Pending: queued, waiting to start
  • Running: currently executing
  • Done: finished successfully
  • Failed: finished with errors
  • Stopped: canceled before completion
Click any action to inspect its steps, current state, and, when available, the full agent session. Action logs

​
What to look for while monitoring

When a run is active, focus on:
  • whether actions are starting as expected
  • which step a failed action stopped on
  • whether failures are isolated to one target or systemic across many targets
If many actions fail in the same place, the problem is usually in the Automation configuration, repository setup, or shared credentials. If only one action fails, the issue is usually specific to that target.

​
Cancel execution

  • Single action: three-dot menu > Cancel
  • Entire run: click Cancel on the run details page
Running actions stop immediately. Pending actions are skipped. Cancel options

​
Review results

After completion:
  • View execution summary (completed/failed/canceled actions, time)
  • Click individual actions to review execution details
  • Check your SCM for pull requests created by the Automation

​
Execution history

View past runs from the Automation’s Execution History section. Each run retains action status and execution details for later inspection. Use history to compare configuration changes over time or to confirm whether a failure started after a workflow, secret, or trigger change.

​
Common follow-ups

After reviewing a run, the next step is usually one of:

​
Next steps