# Make Scenario Errors: Fix the 8 You'll Meet First > Common Make scenario errors and fixes: ConnectionError, InvalidAccessTokenError, DataError, BundleValidationError, RateLimitError and a bad Form ID. Source: https://learn.ynteractive.com/content/blog/make-scenario-errors · Updated 2026-10-20 · Free from Stepthrough (https://learn.ynteractive.com) Quick answer A [Make scenario](https://learn.ynteractive.com/content/glossary/make-scenario) error shows up as a red module with a type such as **DataError**, **BundleValidationError** or **ConnectionError**, plus a message. The type tells you where to look: connection errors are about the login, data and validation errors are about what you mapped, and rate-limit errors are about how fast you're going. Click the red module's bubble to read the full message before you change anything. The free [first Make scenario lesson](https://learn.ynteractive.com/content/make-com-google-forms-to-google-sheets) shows a working run to compare with. Last updated October 20, 2026 [Take the free module →](https://learn.ynteractive.com/courses/ai-for-medical-dental-admin/9)Module 9 of the free [AI for Medical & Dental Office Admin](https://learn.ynteractive.com/courses/ai-for-medical-dental-admin) course, about 12 minutes. No account needed. By [Robert Breen](https://learn.ynteractive.com/content/about) · Published October 20, 2026 · Updated October 20, 2026 · 4 min read Make · Troubleshooting · Errors ## How do I read a Make error? Open the scenario's **History**, open the failed run and click the bubble on the red module. The output shows the error type, the message and the bundle that caused it. Input is what went in, output is what came back. Comparing the two usually points at the field that caused the problem. ## The common errors and what to do | Error | What it means | First fix | | --- | --- | --- | | ConnectionError | Make could not reach the service | Retry; check the service's status page. Usually temporary. | | InvalidAccessTokenError / "connection expired" | The Google or Gmail login is no longer valid | Reauthorize the connection under Connections, or create a new one with the right account. | | DataError | A value has the wrong type or format | Check the mapped field: text where a number or date was expected is the usual cause. | | BundleValidationError | A required field is empty or invalid | Find the field marked required in the module and map a value, or filter out bundles where it is missing. | | RateLimitError | Too many requests too fast | Slow down: add a Sleep module, or process fewer bundles per run. | | IncompleteDataError | The service sent back partial data | Retry; check that a file or record finished uploading before the scenario reads it. | | "Form not found" / 404 on Google Forms | The Form ID is wrong | Copy the ID from the form's address bar again (see below). | | Gmail: recipient invalid | The To address is empty or malformed | Add a filter with Email **Exists** before the Gmail module. | ## Why does Google Forms Watch Responses fail? Usually the Form ID. Make needs the long code from the form's editor address, between **/d/** and **/edit**. In the lesson you click the **Google Forms** tab, copy that part of the address bar and paste it into **Form ID**. Copying the whole address, or the ID from the "Send" link, which is a different URL, gives a not-found error. The connection must also belong to the Google account that owns the form. ## Why does Google Sheets say it can't find the sheet? The spreadsheet was renamed, moved, or belongs to another Google account, or the tab name changed. Reopen the module, pick the spreadsheet with **Click here to choose file**, open **Sheet Name** and pick the tab again. [Make Google Sheets Modules](https://learn.ynteractive.com/content/blog/make-google-sheets-modules) covers the setup. ## Why did my scenario turn itself off? When a scheduled scenario fails several times in a row, Make deactivates it so it doesn't keep failing. Fix the cause, then switch it back on. You can change how many consecutive errors are allowed in the scenario's settings. ## How do I stop one bad bundle from stopping everything? Add an error handler route to the module that fails: right-click it, choose **Add error handler** and pick a directive such as **Ignore** (skip this bundle and carry on) or **Resume** (use a fallback value). Use Ignore only when someone will notice the skipped item; a quiet failure is worse than a loud one. The idea is the same as [error handling](https://learn.ynteractive.com/content/glossary/error-handling) in any [automation](https://learn.ynteractive.com/content/glossary/automation) tool. ## Try it free, step by step **Your First Make.com Scenario: Google Forms to Google Sheets**. Build your first Make.com scenario: every new Google Forms response becomes a new row in Google Sheets. Trigger, connection, mapping, Run once and a schedule. You do every step yourself in a practice copy of Make, it checks your work as you go, and “Do it for me” finishes any step you get stuck on. Free, and nothing touches your real accounts. [Start the free lesson](https://learn.ynteractive.com/modules/make-first-scenario) [Or read the full step-by-step guide](https://learn.ynteractive.com/content/make-com-google-forms-to-google-sheets) ## How do I prevent errors in the first place? - Test with **Run once** and read the bubbles before you turn a scenario on. - Filter out incomplete data early, like rows with no email. - Name connections by account, so you never pick the wrong Google login. - After changing a form or sheet, re-open the modules that use it. The [Filters and Routers](https://learn.ynteractive.com/content/make-com-router-and-filters) and [daily summary](https://learn.ynteractive.com/content/make-com-daily-summary-email-google-sheets-schedule) lessons both end with a test run you can learn to read. ## Key takeaways - The error type points at the cause: connection, data, validation or [rate limit](https://learn.ynteractive.com/content/glossary/rate-limit). - Read the red module's bubble (input and output) before changing anything. - A wrong Form ID or a connection for the wrong account causes most first-scenario failures. - Make turns a scenario off after repeated errors; fix the cause, then switch it on. ## Frequently asked questions **What is a DataError in Make?** It means a module received a value it can't use, such as text in a number field or a date in the wrong format. Fix the mapping or convert the value with a function first. **How do I reconnect Google in Make?** Open Connections in the left menu, find the Google connection and click Reauthorize, or create a new connection in the module and sign in with the right account. **Can Make retry failed runs automatically?** Yes. Incomplete executions can be stored and retried, and the Break error handler retries a module a set number of times. Turn on storing incomplete executions in the scenario settings. **Is there a free course on Make?** Yes, [Make & Zapier Jump Start](https://learn.ynteractive.com/courses/make-zapier-jump-start) is free and practice-based. ## Free lessons in this post - [Your First Make.com Scenario: Google Forms to Google Sheets](https://learn.ynteractive.com/content/make-com-google-forms-to-google-sheets): Build your first Make.com scenario: every new Google Forms response becomes a new row in Google Sheets. Trigger, connection, mapping, Run once and a schedule. - [Filters and Routers in Make.com: Send Urgent Requests One Way, Routine Ones Another](https://learn.ynteractive.com/content/make-com-router-and-filters): Add a router to your Make scenario, email the front desk about urgent requests with a filter, and send everything else to Google Sheets with a fallback route. - [On a Schedule: A Daily Summary Email from a Google Sheet in Make.com](https://learn.ynteractive.com/content/make-com-daily-summary-email-google-sheets-schedule): Build a Make scenario that runs every day at 5 PM, finds today's rows in Google Sheets, combines them with a Text aggregator and emails one summary with Gmail. ## Related terms Plain-English definitions, each with an example from a free lesson. [Scenario (Make)](https://learn.ynteractive.com/content/glossary/make-scenario) · [Automation](https://learn.ynteractive.com/content/glossary/automation) · [Rate limit](https://learn.ynteractive.com/content/glossary/rate-limit) · [Aggregator (Make)](https://learn.ynteractive.com/content/glossary/make-aggregator) · [Bundle (Make)](https://learn.ynteractive.com/content/glossary/make-bundle) · [Credits (Make)](https://learn.ynteractive.com/content/glossary/make-credits) · [Iterator (Make)](https://learn.ynteractive.com/content/glossary/make-iterator) · [Module (Make)](https://learn.ynteractive.com/content/glossary/make-module) [The full AI glossary](https://learn.ynteractive.com/content/glossary) ## Related prompts - [End of day report prompt](https://learn.ynteractive.com/content/prompts/end-of-day-report-prompt): A ChatGPT prompt for an end of day report: paste your rough notes and get a short EOD report with what got done, what is still… [All free prompt templates](https://learn.ynteractive.com/content/prompts) ## Keep reading - [Make Scenario Not Running on Schedule? Check These](https://learn.ynteractive.com/content/blog/make-scenario-not-running): A Make scenario that never runs on its own is usually off, in the wrong time zone, waiting on new data or out of operations. How to check each. - [Make Router and Filter Examples: Send Data Two Ways](https://learn.ynteractive.com/content/blog/make-router-filter-examples): How a Make router and filters split one scenario into routes: urgent vs routine, a fallback route, route order and five filter setups you can copy. - [Make Filter Operators Cheat Sheet: Text, Number, Date](https://learn.ynteractive.com/content/blog/make-filter-operators-cheat-sheet): Every Make filter operator group on one page: text, numeric, date, basic and array, with an office example for each and the mistakes that block bundles. [All blog posts](https://learn.ynteractive.com/content/blog) · [All free tutorials](https://learn.ynteractive.com/content)