Replaying Runs

A replay runs a finished run again as a new run: the same workflow, the same form entry. Use it after fixing the cause of a failure, such as a missing credential, a wrong folder id or a service that was down.

How to replay a run

1. Fix the cause: update the workflow, store the credential, or wait for the other service.
2. Open the run in FlowMint Workflows → Run History.
3. Select Replay this run. The button appears on Completed, Failed and Cancelled runs.
4. FlowMint opens the new run’s page. It starts QUEUED; refresh until it finishes.

An assistant can do the same with flowmint_replay_run, which returns the new run’s number.

What a replay does

• It runs the workflow as it is now, from the first step. Changes you made since the original run apply.
• It reads the entry as it is now. If the entry was changed, it uses the new values; if it was deleted, the form data is empty.
• It repeats every step’s effect. Emails are sent again, a new Printavo quote is created, HTTP posts are sent again. Steps that find before they create, such as drive_find_or_create_folder, reuse what the first run made. The full list is in Conditions and errors.
• It runs even if the workflow is disabled.
• The original run is unchanged. The new run records which run it replays.

A replay cannot start from a later step or change the data it runs with. To skip steps that already worked, add a temporary skip_if to them, replay, then remove it.

Runs you cannot replay

Only finished runs can be replayed. A run that is QUEUED or RUNNING cannot, and there is no way to cancel a run from FlowMint. Disabling or editing the workflow does not stop runs already queued.

To stop a queued run before it starts, open Tools → Scheduled Actions, find the pending fmw_run_workflow action whose argument is the run number, and choose Cancel. The run then stays QUEUED in Run History for good; to run that submission later, trigger a fresh run another way, such as a new submission.

A run in QUEUED with a Retry count of 1 or more is waiting for an automatic retry; see Conditions and errors. It finishes on its own. Up to version 0.9.0 such a run never started; the update marks it Failed (retry_stranded) so you can replay it.

Related pages

• Viewing Runs — Find a run in FlowMint Workflows → Run History, read its status and each step's output or error, and know what the record keeps and for how long.
• Conditions and Errors — Skip steps with skip_if, branch with conditional, recover with try_catch and on_error, and what happens to a run that fails, including automatic retries.
• Failure Notifications — The alert FlowMint sends when a run fails for good — to Slack if a webhook is stored, otherwise by email — what it contains, and how to route or silence it.
• Testing Workflows — Validate a workflow, stage it switched off, run it with a real submission, and read the recorded config and output before you let it run for visitors.