I added Retry to every Make.com scenario I publish. Two of them still couldn't retry anything.
On 11 November I went through the free Make.com scenarios I publish for Shopify stores and replaced every Ignore error handler with Retry , and switched on Store incomplete executions . Failed calls would now be retried three times, fifteen minutes apart, then kept for re-running instead of being thrown away. Job done. The next day I opened two of them again and found the fix did nothing for the…
On 11th November, I reviewed the free Make.com scenarios I shared for Shopify stores. I replaced every "Ignore error" handler with a "Retry" and enabled "Store incomplete executions." When failures occurred, the three modifications failed to resolve the issues. The next day, I tested these two scenarios and discovered the fix had no effect on their failures.
Make.com's HTTP module has an advanced setting: "Return error if HTTP request fails." The module treats 4xx and 5xx responses as errors when this setting is on. When the setting is off, responses like 400 or 500 are not considered errors, and the scenario history shows a success. My Retry handler had no errors to catch because the HTTP module did not treat error replies as errors.
This mistake hid an earlier failure. Meta's Graph API version was retired in May 2026. Every request returned a 400 error, and every run finished green for about four months. Three settings concealed this error: the HTTP module did not treat error responses as errors, the step's handler was set to "Ignore," and failed runs were not stored.
I fixed two of the three settings. On two scenarios, the third setting remained unchecked. Both scenarios were set to "No," allowing hidden failures. I identified this by manually checking the setting, not by any alerts or notifications. The error handler is visible on the canvas, while the setting is located under "Show advanced settings" at the bottom of the HTTP module.
This setting is often overlooked because it appears after scrolling through numerous options. When every scenario that calls an external API is checked, you should verify the following: every step with data out has an error handler set to "Retry" (previously "Skip"), "Return error if HTTP request fails" is enabled in the HTTP module, and "Store incomplete executions" is set to "Yes."
When automating processes, it's crucial to check these settings to ensure broken manual processes don't go unnoticed. Automated processes often lack visible issues.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
