How to Fix Common Make.com Errors (Beginner Troubleshooting Guide)

1. Understand the Error

• Execution History:Go to your scenario’s history and find the failed run. Click on the red module to see the detailed error message and input/output data.
• Error Types:Common issues include API rate limits connection problems, or incorrect data types/missing fields. 

2. Implement Error Handling (The Key Step)

• Add Handler:Right-click the module that’s failing and select “Add error handler”.
• Choose a Strategy:
  • Break:Stops the scenario if that module fails (good for critical steps).
  • Retry:Tries the operation again after a delay (great for temporary API issues).
  • Ignore/Resume:Logs the error and continues with the next item (useful for batch processing).
  • Fallback:Switches to an alternate route or service. 

3. Common Error Fixes

• Connection Issues:Re-authenticate the app connection, check API keys, or verify the service is online.
• Data Mapping:Ensure you’re mapping the correct data from previous modules. A string being sent where a number is expected often causes errors.
• API Limits:If you see a RateLimitError, use the ‘Retry’ error handler or add a delay (pause) module before the failing step to slow down requests, suggest this Make article and this Make article.
• Syntax/Logic:For custom code (set variables Run Script) check for missing brackets or incorrect syntax. 

4. General Troubleshooting Tips

• One Thing at a Time:Make one change, then test.
• Simplify:Temporarily remove complex parts to find the source of the problem.
• Use Tools:Utilize Make’s built-in “Check” feature in modules and the scenario visualizer. 

1. Identify the Error Type

When a scenario fails, look for the red bubble above the affected module. Click it to see the specific error message. 

• Data Mapping Issues:Occurs when a module receives data in the wrong format (e.g., text instead of a number) or is missing required fields.
• Connection/Authorization Errors:These happen when an API key or OAuth token expires. You can fix this by going to the Connections tab and clicking Reauthorize.
• Rate Limiting (429 Error):The external service is receiving too many requests at once. This usually requires adding a delay or using a retry strategy.
• Silent Errors:The scenario runs successfully (green bubbles), but the output is incorrect. You must manually check the input and output data of each module to find where the logic failed. 

2. Common Fixes for Beginners

• Check Input/Output:Always click the “1” bubble to check out exactly what data enter the module. If “Source is not the valid JSON” appears, certains the previous module is correct way formatting a data.
• Verify Connections:If the module fails immediately, go to a Connections list in a sidebar to verify and re-verify the app access.

Use the Make DevTool: For advanced debugging, the Make DevTool browser extension permit you to check out the raw API requests and responses.

3. Implementing Error Handlers

Instead of letting a scenario stop, you could righteous-click the module and select Add error handler to defined a fallback path. 

• Ignore:Skips the error and continues a scenario as if nothing occured.
• Break:Stored the failed data as an “Incomplete Execution.” This was ideal for temporary API downtime as it permits to automatic retries later.
• Resume:Provides the substitute value for the failed module so rest of the scenario could usage it.
• Rollback:Stops the complete scenario and undoes some previous steps (if the app supports it) to maintain data integrity. 

4. Advanced Retry Strategies

If you expect frequent temporary failures, utilizing the Break module settings to configured: 

1. Number of attempts:How much times Make must tried again (default is 3).
2. Interval:How longer to wait between attempts (default is 15 minutes).
3. Allow Incomplete Executions:You should enabled this in Scenario Settings to the Breaking module to function.