Feature Request
Problem
Currently there's no visibility into how long jobs and workflows spend waiting in the queue before they start executing. This makes it hard to identify bottlenecks and capacity issues.
Proposed Solution
Track and display queue time (time spent waiting before execution starts) for both Jobs and Workflows:
- Capture queue time — Calculate the difference between when a job/workflow is queued and when it actually starts running. Store this as a field on the job/workflow record.
- Display in execution details — Show queue/wait time as part of the job and workflow detail views alongside existing timing info.
- Queue time metrics — Add an aggregate metric showing average wait times (per repo, per workflow, over time) to the dashboard/stats views.
Implementation Notes
- For workflows:
queued_at → run_started_at
- For jobs:
created_at → started_at (from workflow_job webhook events)
- New fields:
queueTime (seconds) on both workflow run and job records
- Dashboard metric: average queue time with trend over configurable time window
Why
- Helps identify runner capacity issues
- Useful for optimizing CI/CD pipeline performance
- Visibility into infrastructure bottlenecks
Feature Request
Problem
Currently there's no visibility into how long jobs and workflows spend waiting in the queue before they start executing. This makes it hard to identify bottlenecks and capacity issues.
Proposed Solution
Track and display queue time (time spent waiting before execution starts) for both Jobs and Workflows:
Implementation Notes
queued_at→run_started_atcreated_at→started_at(fromworkflow_jobwebhook events)queueTime(seconds) on both workflow run and job recordsWhy