Reprocess an existing run
20s · 3 steps
Re-fire a previous run with its original trigger payload — useful for email-triggered agents you don't want to wait on.
Every stored run keeps a copy of the trigger payload that started it (the inbound email, the webhook body, the schedule tick, or the manual input). The Reprocess button replays that payload through a fresh run so you can re-test an agent against a real input without waiting for the next email / schedule / webhook to arrive.
Reprocess is different from Resume: • Resume (only on failed runs) replays cached outputs of successful nodes and restarts at the failed node. Side-effect nodes that already fired do NOT re-fire. • Reprocess (any terminal run) runs the agent from node 0 with the same trigger input. EVERY node re-executes — including side-effect nodes like email.send or tally.create-voucher. Treat it like 'Run again with the same input.'
The new run shows up in the left pane and the audit view jumps to it automatically.
Steps
- Open the Runs tab and pick a past run.
Any succeeded, failed, or cancelled run works. The trigger payload is shown in the audit-trail view as the first card (kind: email, kind: manual, etc.).
- Click 'Reprocess' in the audit header.
Top-right of the Run audit trail card, below the status badge. Disabled with a tooltip when the run pre-dates the trigger-payload field (legacy runs).
- Watch the new run stream live.
A fresh run is created and the audit pane jumps to it. Side-effect nodes WILL re-fire — if the agent sends emails or writes to Tally, those actions happen again.
Live recipes need the desktop
This article is a static preview. The in-app Help sidecar inside Avery NXR can fire each step against your live project — install the desktop to use it interactively.