> Source: https://www.gitdash.info/docs/feat-workflow · GitDash v4.7.1

# Workflow detail

`/repos/[owner]/[repo]/workflows/[id]`

Overview Runs Performance Reliability Triggers DORA

One workflow in depth. The header summarizes success rate, average duration, p95 queue wait, time to recover, re-run rate and developer time lost, above the last 40 runs.

![Workflow detail overview](https://www.gitdash.info/screenshots/workflow-detail.jpg)

| Tab | What it shows | Feature |
| --- | --- | --- |
| Overview | Why it is failing, where the time goes, recent runs and concrete ways to speed it up. | — |
| Runs | Every run with commit, branch, attempt, queue wait and duration; sortable, filterable, exportable. | — |
| Performance | Job duration (average vs. p95), job composition per run and the slowest steps. | `performanceTab` |
| Reliability | Pass/fail timeline, flaky branches, anomaly detection and AI failure hypotheses. | `reliabilityTab`, `anomalyDetection` |
| Triggers | Trigger events, top branches, hour of day, day of week and who triggers runs. | — |
| DORA | The workflow's own DORA levels, as a build-pipeline proxy. | — |

With `githubIssueFromAnomaly` on, an anomaly can be filed as a GitHub issue from a confirmation dialog, using your own token. It is off by default and excluded from “Enable all”, because it writes to GitHub.