# Reviewing failed runs

Open the first failed step, capture its error and preceding input, distinguish configuration from transient failure, and preserve logs before changing anything.

![Reviewing failed runs in Foxora Desktop v5.0.3](/docs/images/v5.0.3/desktop/task-transcript.webp)

## Where this lives

Open a task and choose **Runs** in its header.

A run is one execution record for an agent, crew, scheduled task, workflow, bot, or channel-triggered job. It contains status, timing, step activity, logs, usage, and outputs.

> **Safety:** Retrying can repeat external actions. Inspect the last confirmed successful step and use idempotency or a corrected input before running again.

## Steps

1. Open a task and choose **Runs** in its header.
2. Reproduce the problem once with the smallest safe input and record the exact message, action, and time.
3. Open the first failed step.
4. Capture its error and preceding input.
5. Distinguish configuration from transient failure.
6. Preserve logs before changing anything.
7. Change one reversible condition, then repeat the same test. Preserve logs or exports before any reset.
8. **Confirm the result.** Check terminal status, output identifiers, logs, usage, and the actual destination rather than relying on a green badge alone.

## Choose the right path

- Start a new run for a new input.
- Retry only a failed or safely repeatable execution.
- Cancel when continuing could waste credits or create an unwanted side effect.


## Confirm it worked

- Check terminal status, output identifiers, logs, usage, and the actual destination rather than relying on a green badge alone.
- The screen, command, file, run, or destination named in this guide reflects the expected state.