A replay is used to replay all or a specific subset of your events to a destination.
Replays are at the core of the Batch platform. Replays allow you to replay events in your collections back to your event bus, helping with data loss and disaster recovery.
For information on what destinations we can replay your data to, please see Destinations.
While Batch does transform and annotate your payloads with additional data for display and indexing purposes, your original payload will be replayed back exactly as it was received, in the format in which it was received.
Creating a Replay
Create a Destination
2. Goto collection and create a query or leave the default of all messages over the last day
3. Confirm collection is returning messages
Query is returning 1 message
3. Select Replay and fill in details selecting destination we created earlier
Monitoring a Replay
Navigate to Replay Tab
Select the Replay name
3. View Replay log
Pausing a Replay
In some cases users may want to pause a replay. There are several possible reasons for this. A destination may need more resources to handle the data coming in. Another possibility maybe the need to make adjustments to production environments such as silencing events that are triggering notifications end users like an email event.
Pausing a Replay
There is a chance that paused events could repeat a few events after being resumed from a pause since messages are processed in batches.
Replay Behavior and Payloads
During a replay, Batch will "push" events to your configured destination.
Replays take ~30 seconds to start up (and can increase from there, as the data is read from S3).
This list describes how the events are pushed and what their payloads look like.