# Review generation progress

The generation progress view shows what TestVibe and GitHub Actions are doing while the AI agent works.

Use it to understand whether generation is waiting, actively working, finalizing output, or blocked.

## Common States

| State      | What it usually means                                                           |
| ---------- | ------------------------------------------------------------------------------- |
| Queued     | GitHub accepted the workflow, but a runner has not started it yet.              |
| Setting up | The runner is preparing dependencies, browser tools, and configuration.         |
| Running    | The agent is generating or validating output.                                   |
| Finalizing | Generation work is done and TestVibe is collecting files, status, or artifacts. |
| Succeeded  | Generation completed and output should be available.                            |
| Failed     | Generation could not complete successfully.                                     |
| Cancelled  | The workflow was stopped before it finished.                                    |

## Overview

The overview summarizes the full generation run. It may show:

* status
* workflow run link
* generated path
* target site
* runner labels
* agent or model details
* section counts
* duration or token usage when available

Use the overview when you want the whole-run status rather than a single scenario.

## Sections And Steps

For Gherkin features, progress may be organized by:

| Section          | What it means                                      |
| ---------------- | -------------------------------------------------- |
| Background       | Shared setup for scenarios in the feature.         |
| Scenario         | One concrete behavior being generated.             |
| Scenario Outline | A scenario pattern generated with example values.  |
| Steps            | Individual actions or assertions inside a section. |

Section progress helps you see whether the agent is working through the feature or stuck on a particular part.

## Live Preview And Evidence

When available, generation may show:

| Evidence           | How it helps                                                        |
| ------------------ | ------------------------------------------------------------------- |
| Screenshot preview | Shows what the browser or agent saw during generation.              |
| Trace link         | Opens deeper Playwright debugging evidence for a generated section. |
| Generated path     | Shows where output is being saved in the repository.                |
| Workflow run link  | Opens GitHub Actions details when you need lower-level logs.        |

## If Progress Looks Stuck

Use this order:

1. Check whether the status is queued or setting up.
2. If queued, check runner availability and labels.
3. If setting up, give the workflow time to install dependencies.
4. If running for a long time, open the workflow link if available.
5. If failed, read the failure message before editing the feature.

For runner-specific issues, see [Troubleshoot runners](/runners/troubleshooting-runners.md).

## After Completion

When generation succeeds, continue to [Read generated output](/ai-generation/read-generated-output.md). When it fails, continue to [Troubleshoot failed generation](/ai-generation/troubleshoot-failed-generation.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/ai-generation/review-generation-progress.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.