Hi Make Community,
I’m encountering an issue with the retry scheduling for a Break module error handler in one of my scenarios, and I’m hoping someone might have some insight.
Here’s my setup:
- I have a scenario where I’ve implemented an error handling route using the Break module.
- Within the Break module’s settings, under the error handler directive options, I have configured it to Retry when an error occurs.
- I’ve set the Interval between attempts to 1 minute.
Expected Behavior:
My understanding is that when the main route encounters an error and triggers this Break handler, the scenario run should pause, be marked as ‘Incomplete’, and automatically schedule a retry attempt 1 minute later.
Actual Behavior:
When an error occurs and the Break handler is triggered, the scenario does get paused and marked as ‘Incomplete’. However, when I check the “Incomplete executions” tab, the scheduled time for the next retry attempt is consistently 5 minutes later than the time the error occurred, not the 1 minute I configured.
Separately, I’ve also felt that the “Incomplete executions” section sometimes behaves a bit unexpectedly or seems generally buggy, but my primary concern right now is this specific 1-minute vs 5-minute discrepancy in the retry scheduling.
-
Has anyone else experienced this? Is there a known reason why a 1-minute retry interval set in the Break module would result in an actual 5-minute scheduling delay?
-
Is there perhaps a minimum retry interval enforced by Make.com (e.g., 5 minutes) regardless of the setting in the Break module?
Any help, insights, or suggestions would be greatly appreciated!
Thanks!