# Workflow still running or stuck

Generation and test runs execute in GitHub Actions. TestVibe shows their live status, but the workflow still depends on GitHub queueing, runner availability, dependency installation, browser startup, test duration, and artifact upload.

## Normal Waiting Points

| State      | What may be happening                                                            |
| ---------- | -------------------------------------------------------------------------------- |
| Queued     | GitHub is waiting for an available runner that matches the requested labels.     |
| Setting up | The runner is checking out code, installing dependencies, or preparing browsers. |
| Running    | Generation or Playwright tests are executing.                                    |
| Finalizing | Reports, screenshots, videos, traces, and callbacks are being uploaded.          |
| Canceling  | GitHub is stopping the workflow and TestVibe is waiting for the final status.    |

## What To Do

1. Refresh the TestVibe run or generation page.
2. Check whether TestVibe links to the GitHub Actions workflow run.
3. If the workflow is queued, check runner availability.
4. If the workflow is running, look for live step progress before canceling.
5. If no status changes for a long time, open the GitHub workflow logs.
6. Cancel and retry only when you have reason to believe the workflow is stuck or the environment was fixed.

## Runner-Related Stalls

If a workflow stays queued, the selected runner may be offline, busy, or missing the labels TestVibe requested. This is especially common with self-hosted runners.

Check:

* the default runner selected in TestVibe settings
* the labels required by the workflow
* whether the self-hosted runner is online in GitHub
* whether the target site is reachable from that runner

See [Troubleshoot runners](/runners/troubleshooting-runners.md).

## When To Cancel

Cancel when:

* you selected the wrong test, URL, branch, or configuration
* the runner is offline and will not come back soon
* the target site is down
* the workflow has made no progress and GitHub logs show no active work
* you fixed a setup issue and need a clean retry

For run controls, see [Cancel or re-run tests](/run-tests/cancel-or-rerun-tests.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/troubleshooting/workflow-running-or-stuck.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.