Beta feature
This is a beta feature, which means we're still developing it. Some functionality may change.
Replay re-runs a trigger-based pipeline using the trigger data captured from its original run, so you don't have to wait for the triggering event to happen again or re-trigger the source system. This article explains when to use Replay, which pipelines support it, and how to replay a run.
When to use Replay
Replay helps in two situations. You can re-run a failed run with the same trigger data, instead of losing the event or rebuilding it by hand. You can also re-run a past trigger while you build or edit a pipeline, instead of triggering the source system again to get new input. In both cases the pipeline runs again in full, including the steps that already completed.
Use Replay
Replay appears in two places. The Activity log shows a Replay option next to each past run, and the filter at the top narrows the list to replayable runs. The pipeline designer shows Replay in the side panel when the pipeline has a recent run.
A run is replayable when all of the following are true:
The pipeline starts with a trigger step, either a poller or a webhook.
The pipeline is turned on. Pipelines that are turned off can't be replayed.
The run is still within the eligibility window.
One exception applies to trigger-based pipelines started by another pipeline.
Replay always runs the pipeline's current setup, not the setup that was in place when the original trigger fired. If you changed steps, mappings, or logic since the original run, the replay uses those changes, and the result can differ from the original run.
You can replay a run for 7 days after it originally ran. After 7 days, the run is no longer eligible for replay.
Before replaying a run
A replay can repeat actions the original run already completed, including record creates, record updates, and calls to external systems. Review the confirmation dialog before you start the replay.
Important
Steps that already ran successfully will run again, so some records or messages may be duplicated.
How to replay a run
Open the Activity log or the pipeline designer.
Select Replay next to an eligible run.
Review the confirmation dialog. It shows the trigger data the replay will use, a preview of the run, and a warning that the replay can repeat actions the original run already completed.
Select Replay to start the run.
The new run appears in the activity log, where you can follow each step as it completes.
The Trigger step's Input field shows the captured JSON payload as read-only. You can review the payload before you replay, but you can't edit it in this beta. Previews of large payloads are truncated.
Limitations
Replay works only for pipelines that start with a trigger step, and it re-runs the whole pipeline regardless of which steps completed successfully in the original run. A run started by another pipeline, or a Callable pipeline, has to be replayed from the pipeline that started it. A run that was already replayed can't be replayed a second time, so replay the latest run instead. The pipeline must be enabled to use Replay. Replay eligibility lasts 7 days from the original run. Previews over 1MB, or over 100 items for bulk triggers, are truncated. The replay itself always uses the full payload.