Running a run again

A service answered 503. A field was spelled wrong. The workflow is fine now, and what you want is not a fresh run on fresh data: it is that mail, that webhook body, through the corrected steps. That is what Run again does.

How it works

The steps come from the canvas as it is now, and what arrived comes from the run as it was. So a change you have saved since is used, and the payload is the original one.

A new run, not a resumption

Run again starts a new run from the first step. Steps that succeeded the first time run again, and a step that sends something sends it again. Nothing can know which side effects of the first run already happened, so nothing pretends to continue where it left off.

Check the steps that send, pay or create before you run a run again. If the first run already sent the mail, the second will send it too. An error route, or a seen before? step from key-value state, can make a workflow safe to repeat.

When it cannot

A run started by hand or by a schedule had nothing in hand, so it can always be run again. A run started by a webhook or by mail needs what arrived, and that is kept with the run up to 32 KB. Run again refuses, and says which reason applies, when the payload:

was larger than that, so nothing was kept rather than half of it;
is too old and no longer available.

Re-running one step

While building, you do not need a whole run to try a change: run a single step again on its last input and see what it returns.