Context: Web, Make community (community.make.com, answered by samliew): "Resuming while Erroring" thread. The fix is adding the Resume error directive to the HTTP module's error routes so a failing request feeds a fallback into the rest of the flow instead of killing the run. Related thread "Flow control, how to call a specific module after it has already been invoked once" uses the same pattern: a search 

[Make community, answered thread]: when a module is allowed to fail, dont let it kill the run. Add the Resume error directive to the module's error route (right-click -> Add error handler -> Resume) and fill in the substitute mapping.

Two patterns from real threads:

1. HTTP module that may 404: Resume with a fallback body (e.g. an empty object or a default record) so downstream modules keep running on the fallback instead of erroring on missing fields.

2. "Call a module after it already ran": a Search module throws when nothing matches. Put Resume on its error route with the mapping that returns the not-found item downstream, and the rest of the scenario treats "nothing found" as data instead of an error.

Resume is the right directive when the failure is expected and you know what the downstream modules should see instead. If the failure is transient (rate limits, outages), Break with retry is the better pick.