Rerun a run

After fixing a failure, rerun the affected run with its original trigger data. Inngest creates a new run and trace using the function code available when that run starts.

Before you rerun

Open the original trace. Check the failed step and every completed side effect. Use Idempotency to prevent repeated effects, and Versioning to understand how a new deployment affects existing runs. A rerun from the beginning repeats the entire function. A rerun from a selected step restores saved outputs from earlier steps, then runs the selected step and later steps again. Some steps let you replace JSON-serializable input before rerunning.

In the dashboard

1. Open the original run in Runs.
2. Choose Rerun in its header to start from the beginning, or select a step and choose Rerun from step.
3. Review the input and create the new run.
4. Open the new trace. Check its results and repeated side effects against the original. Cron-triggered runs cannot be rerun. A step ID must identify one step in the original run for CLI or API rerun-from-step. Use Replay runs in bulk for many runs from one incident.