Make Not Working? Common Errors & Fixes
The 11 Make problems users hit most often, why they happen, and the fixes that actually work — collected from user reports, forums, and official support docs.
Make Webhook Not Triggering Scenario
Workaround availableWebA Make webhook that doesn't start the scenario usually means the scenario is off or scheduled rather than instant, the data structure is stale, or the webhook was deactivated. Turn the scenario on with 'Immediately' scheduling, re-determine the data structure and check the webhook's Logs and Queue.
Make Webhook 'Queue Is Full' or 410 Gone Error
Workaround availableWebMake returns 400 'Queue is full' when a webhook's queue hits its plan limit (667 items per 10,000 monthly credits, max 10,000) and 410 Gone when a webhook has had no scenario attached for over 5 days. Clear the queue and turn the scenario on, or reattach the webhook.
Make Using Too Many Credits (Operations)
Workaround availableWebMake burns credits fastest through polling triggers, which cost 1 credit per check even when nothing is found, and through loops that run many modules per bundle. Switch to webhooks, poll less often and filter right after the trigger.
Make Scenario Turned Off Automatically
Workaround availableWebMake disables a scenario's schedule after errors across several consecutive runs, and immediately on fatal errors like DataSizeLimitExceededError. Outages have also auto-disabled scenarios. Find the failing module in History, fix it, then switch the scenario back on.
Make 'Invalid Refresh Token, Please Reauthorize the Connection' Error
Workaround availableWebThis error (often shown as invalid_grant) means the OAuth token for Gmail, Google Drive or Microsoft 365 expired or was revoked. Reauthorize on the Connections page; if it recurs about every 7 days, your custom Google Cloud app is still in testing mode and must be published.
Make RateLimitError (429 Too Many Requests)
Workaround availableWebRateLimitError is the HTTP 429 response from the connected app (or from Make's own webhook limit of 300 requests per 10 seconds). The app's limit is shared across all your scenarios, so slow the scenario down with sequential processing, sleeps or batching.
Make ExecutionInterruptedError (Scenario Timeout)
Workaround availableWebExecutionInterruptedError means the run exceeded Make's maximum execution time: 40 minutes on paid plans, 5 minutes on Free. Remaining bundles aren't processed. Split the job into smaller chained scenarios and lower search limits.
Make Google Sheets Watch New Rows Not Working
Workaround availableWebWatch New Rows is a polling trigger that tracks row positions, not content. It skips rows added after a blank row, ignores rows re-added where rows were deleted, and won't fire if the scenario only runs on demand. Reset the starting point or use Search Rows with a status column.
Make BundleValidationError: Missing Value of Required Parameter
Workaround availableWebBundleValidationError means a module received a bundle with an empty required field or the wrong data type, usually because an earlier search returned nothing. Add a filter before the module, use ifempty(), or add a Skip error handler.
Make DataSizeLimitExceededError
Workaround availableWebDataSizeLimitExceededError is a fatal error tied to your plan's data transfer or file size limits; Make immediately disables the scenario regardless of the consecutive-errors setting. Reduce the data passed through the scenario or buy extra credits / upgrade.
Is Make Down? Scenarios Not Running
Fixed in latest versionWebIf many scenarios stop at once, check status.make.com. Recent incidents (Sept 2025, Dec 2025, March, July, Aug and Oct 2026) stopped executions, left webhooks unprocessed and auto-disabled scenarios that had to be re-enabled.
Problem not listed? See all Make complaints or compare Make alternatives.