Run History
The central hub for monitoring, auditing, and managing your CI/CD pipelines in Monk CI.
The Run History dashboard is the central hub for monitoring, auditing, and managing your CI/CD pipelines in Monk CI. It provides a real-time overview of all automated workflows - letting you track performance, identify bottlenecks, and debug failures with precision.
Dashboard Overview
The dashboard is designed for high-density information retrieval, organized by individual workflow runs. Each entry delivers an at-a-glance snapshot of execution status, trigger source, and duration - giving your team everything needed to act fast.
Real-time Status Tracking
View live updates of running, queued, or completed jobs as they happen - no manual refresh required.
Granular Filtering
Narrow down results by status, user, trigger type, or repository to zero in on exactly what matters.
Time-Range Scoping
Analyze performance trends over specific intervals from the last hour to the past 6 months.
Run Status Types
Every run in the feed is tagged with one of four statuses. Use these to triage your pipeline health at a glance.
| Status | Description |
|---|---|
Success | The workflow completed all steps without errors. |
Failed | An error was encountered, causing the run to halt prematurely. |
Running | The workflow is currently being executed by an active runner. |
Queued | The workflow is waiting for an available runner to begin execution. |
Tip: Focus on Failures First
Use the Status Filter to isolate Failed runs. This surfaces actionable issues immediately, so your team can prioritize fixes without scanning through successful runs.
Execution Details
Each run card surfaces the metadata your team needs for debugging and version traceability.
Workflow Name - The title of the job as defined in your YAML configuration file.
Execution Metadata - Displays how long ago the run started and the total Finished in duration for performance benchmarking.
Trigger Type - Iconographic indicators showing whether the run was triggered by a Merge, Push, Schedule, or Workflow Dispatch event.
Global Filter Controls
Located at the top of the run feed, these controls help you cut through noise and surface exactly the data you need.
Filter the feed to show only runs matching a specific status - for example, display only Failed runs to focus your team on immediate fixes without distraction.
Sort by automation type: Push, Merge, Schedule, or Workflow Dispatch. Useful for auditing scheduled jobs or reviewing deployment-triggered pipelines independently.
Isolate activity by a specific developer or project repository. Ideal for team leads auditing individual contributor activity or scoping a single service's pipeline history.
Use the quick-toggle buttons in the top-right corner to switch between time ranges:
1h · 2h · 6h · 12h · 1d · 7d · 1M · 6M
Longer intervals are best for identifying regression patterns or recurring failures over time.
Accessing YAML Configurations
For any run in the feed, you can inspect the exact YAML configuration that was used during that specific execution.
How to Access
Click the View YAML File button on the right side of any run card. This opens a read-only view of the configuration as it existed at the time of the run - including environment variables, step definitions, and runner settings.
This is especially useful when:
- Verifying that the correct environment variables were in scope during a failed run
- Comparing configurations between a passing and failing run on the same branch
- Auditing changes to step definitions after a regression is introduced
Pricing
No Additional Cost
Run History is included in all Monk CI plans at no extra charge. For details on overall platform pricing, visit the Pricing page.