> ## Documentation Index
> Fetch the complete documentation index at: https://xura.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# The 4 stages

> How Gather / Analyse / Review / Act tabs work in the run panel.

Every Flow run — ad-hoc or saved — flows through four stages, shown as sticky tabs at the top of the run panel.

## The stages

<CardGroup cols={2}>
  <Card title="Gather" icon="database">
    Data nodes query your connected sources. You see one row per query with the entity name and rows returned.
  </Card>

  <Card title="Analyse" icon="sparkles">
    Agent / reasoning nodes process the gathered data. Findings are computed here.
  </Card>

  <Card title="Review" icon="lock">
    If there's an approval gate, Xura pauses here with findings + proposed action. You approve or cancel.
  </Card>

  <Card title="Act" icon="zap">
    Action nodes execute. Emails sent, tickets created, records updated.
  </Card>
</CardGroup>

## Auto-advance behavior

Tabs advance automatically as SSE events flow:

* First query starts → **Gather** tab active.
* All queries done → **Analyse** activates.
* `gate` event received → **Review** activates.
* First action starts → **Act** activates.

If the user clicks a tab manually, auto-advance stops — you stay where you clicked. This prevents Xura from yanking you forward while you're inspecting a past stage.

## Locked tabs

Tabs ahead of the current stage are **locked** with a padlock icon. You can't jump to Act before Review is done. Past tabs are always clickable.

## Approve → jump to Act

When you click **Approve & continue** on the Review tab, Xura auto-jumps to the Act tab even if you'd manually pinned yourself elsewhere. This overrides the "user is browsing" behavior — approval is explicit intent to move forward.

## What you see per stage

Every stage panel has:

* **Stage header** — icon + title + dynamic subtitle.
  * Subtitle reads *"Running: `<step label>`"* while a step is in-flight.
  * After completion: *"N steps completed."*.
* **Step list** — one row per SSE step\_start / step\_done event. Rows show:
  * Indicator (spinner while running, check when done, X on error).
  * Label (from the node's `data.label`).
  * Detail chip (from the step's summary — row counts, tool outputs, etc.).