From the execution history view in Zoho Flow, each logged execution has a re-run option. Clicking re-run replays the exact same trigger payload through the current version of the flow. The re-run is processed as a new execution and appears as a separate record in the execution history, linked to the original. This means the flow steps that have been edited since the original execution will apply; the re-run uses the trigger data from the past execution but runs through the flow as it exists now.
Use re-run when a flow execution failed due to a transient issue: a connected app was temporarily unavailable, an API rate limit was hit, or a network timeout occurred. Before re-running, confirm that the underlying issue has been resolved. Also use re-run after fixing a flow configuration error that caused previous executions to fail, to process the backlog of affected records. Avoid re-running executions from flows that create records if the original execution partially succeeded, as this can create duplicates in target apps.
Re-run uses the trigger data from the past execution, but it applies the current flow configuration. If you edited the flow between the original execution and the re-run, the re-run may behave differently from the original, including skipping steps that have been removed or executing new steps that were added. Always verify the current flow configuration before re-running to ensure the expected behaviour. For flows that create records in target apps, check whether the target app has duplicate detection to prevent re-runs from inserting duplicate entries.
Yes. A re-run is treated as a new execution and counts against your plan’s monthly execution limit, just like any regular triggered execution. If you need to re-run a large number of failed executions, check your remaining execution count for the month before proceeding, particularly if the re-runs are for a high-frequency flow.
Yes, technically you can re-run any past execution, not only failed ones. Re-running a successful execution replays the same trigger data through the updated flow, which is a practical way to test a flow edit using real historical data rather than constructing test data manually. Be aware that this will attempt to perform all actions in the flow again, which may create duplicate records in connected apps if those apps do not deduplicate on re-submission.
Aaxonix is a certified Zoho implementation partner based in Pune. Architecture-first, no surprises.