Cheat sheet · Make.com · Errors

Make.com error cheat sheet (2026)

Short answer: Every Make.com error has a type, such as ConnectionError, DataError or RateLimitError, and the type tells you what to do next. Temporary errors (connection problems, rate limits, timeouts) are retried automatically when Store incomplete executions is on, and the Retry handler covers other temporary failures. Data and configuration errors need a fix in the mapping or the setup. Scheduled scenarios switch off after 3 errors in a row by default, scenarios with an instant trigger (such as a webhook) after the first error, and a few fatal errors, such as running out of credits, switch a scenario off immediately.

By Flowpaja · Published

This page contains an affiliate link, marked “affiliate link”.

Make.com error cheat sheet: a RateLimitError 429 retried later, a fatal AccountValidationError switching the scenario off, and the free 2-page PDF
All common Make.com errors on one page. The printable PDF is free, no sign-up.
Disclosure: everything in this guide works with plain Make.com and the apps it connects. At the end we mention our own Make templates and our Make scenario fix service on Fiverr. Module names, settings and limits were checked against Make's errors and warnings docs and error handling overview in October 2026. Menus and limits change, so check them if something looks different.

Names changed in May 2026:

  • Ignore is now Skip, and Break is now Retry. Resume, Rollback and Commit kept their names.
  • Exported blueprints still use builtin:Ignore and builtin:Break (plus builtin:Resume, builtin:Rollback, builtin:Commit).
  • Make bills in credits. The out-of-credits error is still called OperationsLimitExceededError.

When does Make switch a scenario off?

  • Scheduled scenarios switch off after the Errors before deactivation limit (default 3) of errors in a row.
  • Instant-trigger scenarios (webhooks, instant app triggers) switch off after the first error.
  • Fatal errors switch any scenario off immediately, whatever the limit (marked ⚠ below).
  • Warnings don't count. A run that ends with a warning keeps the scenario on.
  • Handled errors change the result: Skip and Resume end the run as a success, Retry and Commit end it with a warning, and Rollback ends it with an error that counts toward the limit. An error route without a handler module (for example only a Slack alert) works like Skip.
  • No handler: with Store incomplete executions off, the run fails like Rollback and counts. With it on, Make stores an incomplete execution and the run ends with a warning (not when the very first module fails).

Make error types

Error typeWhat it meansTypical causeFirst fix to tryHandler that fitsSwitches the scenario off?
ConnectionErrorThe app is unavailable (Make uses this for 502, 503, 504)Outage or maintenance at the serviceWait; check the service's status pageNone needed with Store incomplete executions on: Make retries it automatically. Retry for your own scheduleNot at first: Make pauses the schedule for about 20 minutes and retries
RateLimitErrorToo many requests to the app (HTTP 429)Bursts of bundles, loops, a shared API quotaFewer items per run, a Sleep module, batch callsAs ConnectionErrorAs ConnectionError
ModuleTimeoutErrorNo response in time (most modules wait 40 or 60 seconds)Slow or overloaded API, large requestRetry; make the request smallerRetry (also auto-retried when incomplete executions are stored)After the limit
DataErrorThe app rejected the data, or a function got the wrong typeText too long, wrong date or number format, text into parseDate()Check the input bundle; fix the mapping. Dates: see Google Sheets date errorsResume with a safe value, or log + SkipAfter the limit
BundleValidationErrorThe bundle failed Make's own check before the module ranEmpty value in a required field, text in a date fieldFix the mapping; filter out empty values before the moduleLog + Skip, or ResumeAfter the limit
DuplicateDataErrorThe app refuses a duplicateSame email or record sent twice, a re-runSearch before create, or update insteadLog + SkipAfter the limit
IncompleteDataErrorThe module got only part of the dataA file still uploading while it's downloadedAdd a delay; try again laterRetryMake pauses about 20 minutes and re-runs; off if it reaches the limit
RuntimeErrorCatch-all: an app error that fits no other typeMany 4xx responses with the app's own messageRead the message in History; usually data or permissionsDepends on the messageAfter the limit
MaxFileSizeExceededErrorThe file is larger than your Make plan allowsLarge attachments or exportsCompress or split the file, or pass a linkLog + SkipAfter the limit
MaxResultsExceededErrorMore results than the module may returnA search without filtersNarrow the search; paginate; lower the limitNone (fix the design)After the limit
⚠ AccountValidationErrorMake can't log in to the app (often with 401 or 403)Changed password, expired credentials, revoked accessCheck the credentials; reconnect or create a new connectionNone: it happens before the run starts, so no handler can catch itImmediately
⚠ InvalidAccessTokenErrorThe connection's access token isn't validExpired or revoked OAuth tokenReauthorize the connectionNone (needs a fix)Immediately
⚠ InvalidConfigurationErrorThe module or scenario setup is wrongDeleted sheet or field, missing required settingOpen the module and fix the setupNone (needs a fix)Immediately
⚠ InconsistencyErrorA rollback couldn't safely undo changesTwo scenarios changing the same data store at onceCheck and fix the data by hand; avoid parallel writesNoneImmediately
⚠ OperationsLimitExceededErrorThe organization is out of creditsUsage above plan, loops, frequent pollingBuy extra credits or upgrade; find what uses themNoneImmediately
⚠ DataSizeLimitExceededErrorThe data transfer quota is used up (it's derived from your credits)Large files or payloadsBuy extra credits or upgradeNoneImmediately

Warnings (the scenario stays on):

WarningWhat it meansFirst fixNote
OutOfSpaceErrorA data store is full, or the incomplete-executions storage is fullDelete old records; raise the limit; Resume into a backup data storeIf incomplete-executions storage is full and Discard data if storage is full is off, Make disables the scenario
ExecutionInterruptedErrorThe run hit the time limit: 45 minutes (10 minutes on the Free plan)Split the scenario; lower search limits; batch API callsRemaining bundles are not processed

More on each handler: Make error handling explained.

HTTP status codes in Make

These appear in the HTTP module and inside app errors. By default Make treats 429 as a RateLimitError, 5xx as a ConnectionError and other 4xx codes as a RuntimeError; 401 and 403 can also show up as AccountValidationError.

In the HTTP module, set Return error if HTTP request fails to Yes (in the older HTTP module: Evaluate all states as errors (except for 2xx and 3xx)). Without it, a 4xx or 5xx response passes as a normal result and no error handler runs.

CodeMeaningUsual fixRetry?
400 Bad RequestThe request is malformed or a value is invalidCheck the body, Content-Type and required fieldsNo
401 UnauthorizedMissing or invalid credentialsReauthorize the connection; check the API keyNo
403 ForbiddenAuthenticated, but not allowedAdd scopes or permissions; share the file; ask an adminNo
404 Not FoundThe resource doesn't exist (for this account)Check IDs, the account, and whether the item was deletedNo
409 ConflictThe resource already exists, or a version conflictUpdate instead of create; search firstNo
410 GoneThe resource was removed for good (e.g. an inactive Make webhook)Create a new resource or URLNo
413 Payload Too LargeThe request body is too bigSend less data, or a file link insteadNo
422 Unprocessable EntityValid format, but the data fails validationRead the error details; fix the valuesNo
429 Too Many RequestsRate limit reachedSlow down; respect Retry-AfterYes
500 Internal Server ErrorError on the service's sideRetry; contact the service if it persistsYes
502 Bad GatewayUpstream error at the serviceRetry laterYes
503 Service UnavailableService overloaded or in maintenanceRetry laterYes
504 Gateway TimeoutThe service didn't answer in timeRetry; send smaller requestsYes

App-specific errors

Google Sheets

ErrorMeaningFix
404 "Requested entity was not found"Wrong spreadsheet ID, or the connected account can't see the fileReselect the file; check which Google account is connected
403 "The caller does not have permission"The file isn't shared with the connected accountShare it, or connect the owner's account
400 "Unable to parse range"The tab was renamed or deletedReselect the sheet (tab) in the module
429 / "Quota exceeded"Google allows 60 read and 60 write requests per minute per userFewer calls: one Search Rows instead of many Get a Cell, fewer items per run
invalid_grant / token expiredThe connection lost accessReauthorize. With your own Google Cloud OAuth client in "Testing" status, tokens expire after 7 days

Search Rows finds nothing? See Search Rows returns nothing.

Gmail

ErrorMeaningFix
invalid_grant / 401Token expired or revokedReauthorize the connection
403 insufficient scopesThe connection lacks a Gmail permissionReauthorize the connection and approve all requested permissions. See Google connection errors
400 "Invalid To header"Bad or empty recipient addressFilter out empty addresses; trim() the address
Sending limit reachedGoogle Workspace: 2,000 messages a day per user (500 on trial accounts); personal Gmail accounts have lower limitsSend fewer emails; the limit resets over a rolling 24 hours

Slack

ErrorMeaningFix
channel_not_foundThe channel value is invalid for this connectionUse the channel ID; invite the app to the channel (with a bot connection, public channels too); check the workspace. See Slack channel_not_found
not_in_channelThe app or user isn't a member of the channel/invite the app to the channel, or join it with the connected user
invalid_authThe token is invalid (or the request came from a blocked IP)Reauthorize the Slack connection
is_archivedThe channel is archivedUnarchive it, or choose another channel
ratelimited (429)Too many messages too fast (about 1 per second per channel)Retry; combine messages

HubSpot

ErrorMeaningFix
409 "Contact already exists. Existing ID: …"Create on an email that already exists (also as a secondary email)Search first, or update the existing ID
400 VALIDATION_ERROR / property doesn't existInvalid value or unknown property nameUse the property's internal name; check the value format
401 / 403 MISSING_SCOPESToken invalid, or the connection lacks scopesReauthorize and approve the contact read/write permissions
429 rate limitToo many API calls in a short time (limits depend on your HubSpot subscription)Retry; reduce calls per run

Shopify

ErrorMeaningFix
401Invalid or revoked accessReconnect the store (in Make's Domain field, enter only your-store from your-store.myshopify.com)
403 / missing scopeThe connection lacks a permissionReconnect and approve all requested permissions
404Order or product not found, or the wrong storeCheck the ID and the connected store
429 throttledAPI limit reached (limits depend on the API and the store's plan)Retry; fewer calls per run
422Validation failed on create or updateRead the field errors; fix the values

Older orders missing? Shopify apps see only the last 60 days of orders unless they have the read_all_orders permission, which Shopify must approve. More in Shopify orders to Google Sheets.

Webhooks (Make custom webhooks)

ErrorMeaningFix
400 "Queue is full"Too many unprocessed requests are waiting (the queue size depends on your credits, up to 10,000 items)Switch the scenario on and fix its errors so the queue drains; delete stale items
410 GoneThe webhook was deactivated because it wasn't connected to a scenario for more than 5 daysConnect it to a scenario again, or create a new webhook and update the sender
Payload over 5 MBThe body is over Make's webhook size limit (5 MB on every plan)Send smaller payloads, or a file link
429 "Too many requests"More than 300 requests in 10 secondsBatch or slow down on the sender side
"Waiting for data" foreverNo request reached this URLCheck the URL; send a test with curl. See webhook not receiving data

Setting up a webhook from scratch: receive webhook data in Google Sheets.

Which handler when

  • Temporary errors (429, 5xx, timeouts, ConnectionError): turn on Store incomplete executions. Make then retries ConnectionError, RateLimitError and ModuleTimeoutError automatically. Use Retry for other temporary failures, or to set your own attempts and interval (default 3 attempts, 15 minutes apart).
  • Bad data in one item that you can safely leave out: log the error, then Skip.
  • An optional value is missing and a safe default exists: Resume with a realistic value, never "TBD".
  • Transactional modules (marked ACID, such as Data store or MySQL) that must be all-or-nothing: Rollback (undo) or Commit (keep). Google Sheets rows, sent emails and HTTP calls are not undone.
  • Auth, permission or configuration errors: no handler fixes these. Send an alert and fix the connection or setup.
  • No handler at all: with Store incomplete executions off, the run fails like Rollback and counts toward deactivation.

More detail: Make error handling explained.

The 3 scenario settings that matter

SettingWhat it doesRecommended
Store incomplete executionsSaves a failed run so you can fix and finish it, or let Make retry it. Required for the Retry handler and for automatic retriesOn, unless the data must not be stored
Errors before deactivationHow many errors in a row before Make switches the scenario off (default 3). Ignored for instant triggers, which switch off on the first errorKeep 3; add alerts rather than raising it
Process data in orderRuns one at a time, in the order received; new runs wait until incomplete executions are resolvedOn for webhooks where order or duplicate checks matter. One unresolved incomplete execution blocks later runs

When a scenario has already switched off, see why a Make scenario stopped running. For step-by-step fixes to the most frequent problems, see common Make scenario errors.

Download: Make.com Error Cheat Sheet (2026), printable PDF (2 pages, A4).

No Make account yet? Create a free Make account (affiliate link).

Ad disclosure: links marked "affiliate link" are ads. If you sign up through them, Flowpaja may earn a commission at no extra cost to you. Error names, settings and limits were checked against Make's Help Center in October 2026. Make changes labels and limits, so check the Help Center if something looks different.

FAQ

What does Retry do in Make.com?
Retry takes the failed bundle out of the run and saves it as an incomplete execution, so the rest of the scenario keeps going. With automatic completion on, Make tries it again with the attempts and interval you set (default 3 attempts, 15 minutes apart); otherwise it waits in the Incomplete executions tab for you. It only works when "Store incomplete executions" is turned on.
Why did Make turn off my scenario?
Scheduled scenarios are switched off after a number of errors in a row, 3 by default ("Errors before deactivation"). Scenarios with an instant trigger, such as a webhook, are switched off after the first error. Fatal errors, such as running out of credits (OperationsLimitExceededError) or a connection Make can't log in with (AccountValidationError), switch a scenario off immediately. Check the first failed run in History for the cause.
Which errors should I retry?
Temporary ones: rate limits (429), server errors (500, 502, 503, 504), timeouts and connection errors. With "Store incomplete executions" on, Make retries ConnectionError, RateLimitError and ModuleTimeoutError automatically. Don't retry 400, 401, 403 or 404 errors; they repeat until you fix the data, the connection or the permissions.
What happened to the Ignore and Break handlers?
Make renamed them in May 2026: Ignore is now Skip, and Break is now Retry. Exported blueprints still use builtin:Ignore and builtin:Break.
Does Rollback undo a Google Sheets row or a sent email?
No. Rollback only undoes changes in modules that support transactions (marked ACID), such as data stores. Rows added to Google Sheets, emails sent and HTTP requests stay as they are.

A scenario keeps failing?

Send the exported blueprint and the error text to our Make scenario fix service on Fiverr. No logins needed.

Stuck on an error in your own Make scenario? Make scenario fix / debugging on Fiverr, from $25: send the exported blueprint and a description of the error, no logins needed.

← All guides · All templates

Make, Slack, Google, Google Sheets and the other app names mentioned are trademarks of their owners. Flowpaja is independent and not affiliated with or endorsed by them. Menus and features change; check the providers' current help.