# Notifications

TestVibe surfaces workflow activity when generation, test runs, scheduled runs, or other repository automation starts, updates, succeeds, or fails.

The main notification surface is the **Activity** view. It groups repository activity into lanes so you can see what is happening now and what needs action.

## Open activity

1. Load a repository workspace.
2. Open **Activity** from the header activity icon or compact navigation menu.
3. Choose a lane.

## Activity lanes

| Lane            | What it shows                                                           |
| --------------- | ----------------------------------------------------------------------- |
| Active          | Workflows that are queued, running, or still updating.                  |
| Needs attention | Failed workflows, failed runs, or activity that likely needs follow-up. |
| History         | Recent completed activity for the repository.                           |

## Workflows you may see

Activity can include:

| Activity              | What it means                                               |
| --------------------- | ----------------------------------------------------------- |
| Feature generation    | TestVibe is creating or updating Gherkin feature content.   |
| Playwright generation | TestVibe is creating runnable Playwright code.              |
| Test run              | Selected tests are running through GitHub Actions.          |
| Scheduled run         | A saved schedule started a run automatically.               |
| Workflow failure      | GitHub or the runner could not complete the requested work. |

## Act on an item

Select an activity item to see details. Depending on the item, you can:

| Action          | Use it for                                                                                |
| --------------- | ----------------------------------------------------------------------------------------- |
| Open            | Go to the most relevant TestVibe detail view, such as run details or generation progress. |
| View GitHub run | Open the matching GitHub Actions workflow run when available.                             |
| Refresh         | Reload the activity list for the selected repository.                                     |
| Filter          | Search within the selected lane.                                                          |

## If an expected item is missing

Check that you are in the right repository, then refresh Activity. If the workflow started in GitHub but does not appear in TestVibe, check whether the repository is connected to the current TestVibe workspace and whether the workflow is one of TestVibe's managed workflows.

For stuck workflow status, see [Workflow still running or stuck](/troubleshooting/workflow-running-or-stuck.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/account-settings/notifications.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.