Introduction to errors and warnings
Sometimes, automation doesn't go the way you planned and takes a wrong turn. When this happens, gives you a warning or an error based on the situation.
You can also assume another point of view on errors and warnings: They protect your by preventing the processing of unexpected data, and therefore saving operations usage.
Errors notify you that your Make encountered an unexpected event that is not handled by an error handler. Because of the situation, you should check the .
A module outputs an error when the module receives incorrect data from the previous modules or the module app. When you open your in the editor, highlights the module that outputs the error with the "Caution" sign:
When a module outputs an error, stops the current run and starts the rollback scenario phase. The rollback phase reverts changes if possible and puts back the polling trigger epoch to the time before the run.
When there are consecutive runs that end with an error, disables further scheduling of the . Disabling the allows you to check the error and prevents consuming operations on runs that finish with an error.
The most common situations when a module outputs an error include:
- Mapping a value to a required field in a module when the value is sometimes empty and causes missing required data.
- When you exhaust your resources in the third-party app. For example, when you can't store more data in the app.
- When the app is unavailable. For example, when the app is down for maintenance.
- When there is a change to your authentication or authorization in the app and you don't update your connection. For example, when your API key expires or when you change teams and lose access to some of the app features.
The best way to deal with errors in your is to use an error handler. An error handler connects to a module with the error handling route. When the module outputs an error, the error handling route activates and runs the error handler.
When all errors are handled, keeps scheduling runs instead of disabling the .
For more information, check the Overview of error handling in Make or pages about error types, error handlers or specific error handling strategies.
When an error happens and the error is not handled by any error handler, sends you an email notification:
also sends out a notification when your gets disabled because of repeated errors.
You can learn more about email notifications and their settings here.
Warnings alert you that there was an issue during the run, but not as serious as an error. Also, can have the warning status when there were errors handled with your error handling.
When a module in a returns a warning, your keeps running and stays enabled. But it's a good idea to check the scenario execution history for the cause of the warning.
The situations when you get a warning include:
- When a module outputs an error, but you have enabled the storing of incomplete executions in the settings.
- When you use up all of the capacity of a data store in your .
- When the duration of the run exceeds the time limit for your subscription.
Learn more about warnings here.