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

# ankra runs

> Inspect and act on the organisation's runs

## ankra runs

Read the organisation's run history and act on the runs that move data. A backup, restore or clone run also carries the plan it was given and every attempt of every step, which is what explains a restore that took an hour.

## ankra runs cancel

Stop a run that is still going. A run that has already finished is refused rather than reported as cancelled.

```bash theme={null}
ankra runs cancel <run-id> [flags]
```

**Flags**

| Flag             | Default | Description                                           |
| ---------------- | ------- | ----------------------------------------------------- |
| `-o`, `--output` |         | Output format: json or yaml (default: human-readable) |
| `--yes`          | `false` | Skip the confirmation prompt                          |

## ankra runs get

Describe one run. A backup, restore or clone also shows the plan it was given and every attempt of every step, with the status, the agent job and the failure excerpt of each.

```bash theme={null}
ankra runs get <run-id> [flags]
```

**Flags**

| Flag             | Default | Description                                           |
| ---------------- | ------- | ----------------------------------------------------- |
| `-o`, `--output` |         | Output format: json or yaml (default: human-readable) |

## ankra runs list

List the organisation's runs, newest first.

Naming a cluster or a stack asks the backup lane's own listing, which carries
each run's data-movement payload; without one, the listing covers every kind
of run the organisation has.

Examples:
ankra runs list --kind backup
ankra runs list --cluster production --status failed
ankra runs list --kind restore --stack shop

```bash theme={null}
ankra runs list [flags]
```

**Flags**

| Flag             | Default | Description                                                                                          |
| ---------------- | ------- | ---------------------------------------------------------------------------------------------------- |
| `--cluster`      |         | Only runs touching this cluster (name or id); asks the backup lane's listing                         |
| `--cursor`       |         | Continue from a previous page's cursor                                                               |
| `--kind`         |         | Only runs of this kind: backup, restore, clone, pipeline, promotion, dr\_drill, environment\_hydrate |
| `--limit`        | `0`     | Page size (server default 50, maximum 100)                                                           |
| `-o`, `--output` |         | Output format: json or yaml (default: human-readable)                                                |
| `--stack`        |         | Only runs touching this stack; asks the backup lane's listing                                        |
| `--status`       |         | Only runs in this status (pending, running, blocked, succeeded, failed, cancelled)                   |

## ankra runs retry

Open a fresh run that resumes a failed backup, restore or clone from the
step that failed.

The answer is the new run, not the old one: the failed row will never move
again, so anything watching it would wait forever.

```bash theme={null}
ankra runs retry <run-id> [flags]
```

**Flags**

| Flag             | Default | Description                                           |
| ---------------- | ------- | ----------------------------------------------------- |
| `-o`, `--output` |         | Output format: json or yaml (default: human-readable) |