> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/dashboard/analytics/run-status.md).

# Run Status

Track the distribution of run outcomes over time

Represents the distribution of the outcomes of your builds/runs over time.

## Metrics

* **Overall runs**: overall runs created during the selected period, regardless of their completion or the end state.
* **Failed runs**: runs that have one or more failed tests. Failed runs count includes cancelled and timed-out tests.
* **Passed runs**: runs that have zero failed tests.
* **Average Pass Rate**: passed runs / overall runs.
* **Trendline**: it can be configured as either a **linear trendline** or a **moving average** for Reported Runs, Passed Runs, Failed Runs, and Pass Rate.

<div data-with-frame="true"><figure><img src="https://3745692499-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmFDEiUa9mr11LUlxDnt%2Fuploads%2FKSTt26NuHaOGKu8FCwTx%2FScreenshot%202026-09-22%20at%2010.09.24.png?alt=media&amp;token=ac5359ff-79eb-4328-86f7-69d8860fba42" alt=""><figcaption><p>Example chart - Run Status</p></figcaption></figure></div>

{% embed url="<https://player.mux.com/v9RcXAzEUOGfuE5LDNw9OVcDK8yp7ZyCEId00e1QAMDs?min-resolution=1080p>" %}
Trendline - Run Status
{% endembed %}

## Related

* [Run Duration](/dashboard/analytics/run-duration.md) - Average duration of runs
* [Run Completion](/dashboard/analytics/run-completion.md) - Run completion status distribution
* [Analytics](/dashboard/analytics.md) - Analytics overview


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.currents.dev/dashboard/analytics/run-status.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.