Error Handler

An error handler is a step that defines what an automation should do when a module fails — instead of the whole run simply stopping and throwing an error. Common strategies: retry (wait and try again, useful for temporary API rate limits or timeouts), resume/ignore (log the failure but continue with the rest of the flow), rollback, or break (stop this run but keep the queue moving). In Make you attach an error handler directly to a module and pick a directive like "Retry," "Resume," "Ignore," or "Break." Why it matters: without error handling, one flaky third-party API call can halt an entire automation and silently drop data. Real integrations fail constantly — networks time out, tokens expire, rate limits trip — so robust automations plan for failure rather than assuming every step succeeds. Practical note: pair retry with exponential backoff for rate-limited APIs, and route unrecoverable errors to a notification (email or Slack) plus a data store or log so nothing is lost when you're not watching.