> 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/spec-file-status/spec-files-status.md).

# Spec Files Status

Playwright Spec files status in Currents Dashboard

A spec file can be in on of the following states:

* **Pending** - the spec file did not start its execution yet
* **Running** - the spec file started its execution and has been running
* **Timedout** - the spec file started its execution but didn't report results to the dashboard before the associated Run's timeout. Read more about [Run Timeouts](/dashboard/runs/run-timeouts.md).
* **Cancelled** - the spec file was running at the time the associated run was cancelled. The system will still accept the spec file's result and it will be marked as <mark style="color:green;">Passed</mark> or <mark style="color:red;">Failed</mark>. If the spec never reports the result, it will be eventually marked as <mark style="color:purple;">Timedout</mark>.
* **Passed** - the spec file reported its results to Currents dashboard and no there were no failed tests detected
* **Failed** - the spec file reported its results to Currents dashboard and there was 1 or more failed or skipped test. Read more about [Test Status](/dashboard/tests/test-status.md).


---

# 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/spec-file-status/spec-files-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.