The Replay Trigger lets you test workflows using historical detection data. It replays past tracks through the state machine, producing the same signals (track_created, track_updated, track_expired) as live detections.
When to use
- Testing workflows before deploying to production
- Debugging a specific track that caused unexpected behavior
- Developing new workflows without needing access to live cameras
- Demonstrating workflow behavior to stakeholders
Data source modes
Replay specific tracks by their UUIDs. Use this when you have a known track you want to re-process. Search for tracks by time range, data source, zone, and object type. Use this to replay a broader set of activity. Processing modes
Like the Detection Webhook Trigger, the Replay Trigger supports both streaming and batch processing modes.
In streaming mode, you can choose between auto replay (tracks are replayed with original timing preserved) or manual replay (step through detections one at a time).
Configuration
Output
The output format is identical to the Detection Webhook Trigger. Your workflow doesn’t need to know whether data is live or replayed — the same check nodes, orchestrator, and action nodes work with both.
Credentials
Requires GraphQL Subscription API credentials.
Keep the Replay Trigger in your workflow but disable it when running live. This gives you an easy way to test at any time by disabling the live trigger and enabling the replay trigger.
