Short answer
Why Is My Make Scenario Processing Old Data?
A Make scenario processes old data when a polling module starts from an earlier point, queued webhook bundles remain, or the source record still qualifies as unprocessed. Pause the scenario, inspect the trigger start point and webhook queue, define a safe cutoff or processed marker, then resume with a controlled limit.
Common causes
- The initial polling position was set to all items or an old date.
- A webhook accumulated bundles while scenario processing was paused.
- Processed state was never written back to the source.
- A date filter compares different timezones or inclusive boundaries.
Diagnostic steps
- Pause downstream side effects before changing the trigger position.
- Check pending webhook bundles and the first module’s chosen starting point.
- Choose a documented cutoff and add a durable processed ID or timestamp rule.
- Run a small limit first and confirm the selected records before full activation.
Example
A newly cloned scenario starts watching orders from the beginning and attempts to resend confirmations. Set it to begin now and test against one new order.
Caveats
Deleting a queue discards events permanently. Export identifiers first when those events may still require processing.