> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.qa.army/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.qa.army/_mcp/server.

# Run Statuses and Errors

> Interpret a run outcome and choose the right next action.

Read the Run's status and available evidence before deciding what to do next.
In the CLI, use `qa-army runs get --run run_...` to inspect an existing Run.
If waiting timed out, the Run may still be active; a timeout is not a product
result. Do not start another Run just to reconnect.

| Outcome     | What it means                                          | Next action                                                |
| ----------- | ------------------------------------------------------ | ---------------------------------------------------------- |
| `PASSED`    | Every required assertion succeeded.                    | Keep the saved coverage current.                           |
| `FAILED`    | The product journey ran and an assertion failed.       | Reproduce and route the product issue.                     |
| `ERROR`     | QA.army could not determine a reliable product result. | Check access, setup, target health, and required evidence. |
| `CANCELLED` | The Run stopped before completion.                     | Decide whether a fresh Run is still needed.                |

Never relabel an `ERROR` as `FAILED` just to make the outcome actionable. The
owner and remedy are different.