# Understand live run status

TestVibe shows live run status while GitHub Actions prepares the job, Playwright executes the selected tests, and the runner uploads evidence.

Use the live status to understand whether the run is waiting, setting up, actively testing, finalizing artifacts, or finished.

## Run states

| State         | What it means                                                                                         |
| ------------- | ----------------------------------------------------------------------------------------------------- |
| Queued        | GitHub has accepted the workflow, but a runner has not started executing it yet.                      |
| Setting up    | The runner is preparing the environment, installing dependencies, or accepting the run configuration. |
| Running tests | Playwright is executing the selected tests against the target site.                                   |
| Finalizing    | The runner is collecting results, screenshots, videos, traces, logs, and summary files.               |
| Passed        | All executed tests completed successfully.                                                            |
| Failed        | One or more tests failed, or the workflow could not complete successfully.                            |
| Cancelled     | The run was stopped before completion.                                                                |

## Per-test rows

At the start of a run, TestVibe may only show the selected feature files or test scope. Detailed executable rows appear after the runner creates the execution plan.

During execution, rows update as Playwright reports status. After the run finishes, open failed rows to inspect evidence such as screenshots, videos, traces, console output, and network details.

## Why statuses can update at different times

TestVibe receives information from GitHub workflow events and from runner status updates. These signals usually arrive close together, but they can land a few moments apart.

For example, GitHub may show that a job is complete while TestVibe is still processing final result files, or TestVibe may show detailed test rows before the GitHub workflow page has refreshed. Give finalizing runs a short moment to settle before deciding the result is missing.

## What to do when a run looks stuck

| Where it is stuck | What to check                                                                               |
| ----------------- | ------------------------------------------------------------------------------------------- |
| Queued            | Runner availability, runner labels, repository permissions, and GitHub Actions limits.      |
| Setting up        | Dependency installation, repository secrets, package lock issues, and configuration errors. |
| Running tests     | Target site availability, login state, test data, and long-running UI steps.                |
| Finalizing        | Artifact upload, trace/video size, and GitHub Actions completion.                           |

If a run is clearly no longer useful, see [Cancel or re-run tests](/run-tests/cancel-or-rerun-tests.md). For runner issues, see [Troubleshoot runners](/runners/troubleshooting-runners.md).


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.testvibe.com/run-tests/understand-live-run-status.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.