Types of errors in Make

A module outputs the AccountValidationError when Make cannot authenticate you in the third-party app. For example, when you change your credentials in the app or your credentials expire and you don't update them in the connection, the app module will output the AccountValidationError.

The AccountValidationError appears also with the HTTP status codes 401 and 403.

If a module outputs the AccountValidationError, the scenario ends with an error. When your scenario finishes with an error for the number of consecutive errors in a row, Make disables the scheduling of your scenario.

To fix the AccountValidationError, review your credentials in the app and the connection in Make. If necessary, create a new connection for the app. If you are getting the AccountValidationError frequently, contact our Support.

A module outputs the BundleValidationError when the bundle entering the module doesn't pass validation. Validation means that before processing a bundle in a module, Make checks whether data types match in the module mappings and whether there are no missing values in the module required fields.

The BundleValidationError appears also with the HTTP status codes 400 and 404.

For example, you get the BundleValidationError when you map text to a module settings field that requires a date, or when you map an empty value to a required field in the module settings.

If a module outputs the BundleValidationError with no error handling, the scenario ends with an error. When your scenario finishes with an error for the number of consecutive errors in a row, Make disables the scheduling of your scenario.

The best way to handle this error is to review your mapping in the module settings.

For tips on how to handle missing data in a scenario check out the article about how to fix missing data errors.

A module outputs the ConnectionError when the third-party app is unavailable. For example, the third-party service might be offline because of maintenance. This error uses the HTTP 502, 503 and 504 status codes.

If a module outputs the ConnectionError with no error handling, the scenario ends with an error. Make repeats the scenario run with increasing time delays.

To fix the ConnectionError, check the article about fixing ConnectionErrors.

A module outputs the DataError when data sent by the module doesn't pass validation on the third-party side. For example, when you try to create a tweet with the Twitter > Create a Tweet module that has more than 280 characters, the Create a Tweet module outputs the DataError because tweets have a maximum length of 280 characters.

Another situation when you get the DataError is when you map an incorrect data type to a function. For example, when you map data with the text data type to the parseDate function.

If a module outputs the DataError with no error handling, the scenario ends with an error. When your scenario finishes with an error for the number of consecutive errors in a row, Make disables the scheduling of your scenario.

To fix the DataError, review your mapping and identify the reason why the error happens. If you cannot fix the error with different mapping, you can use the Resume and Ignore error handlers.

A module outputs the DataSizeLimitExceededError when you run out of data transfer quota. Your data transfer limit is calculated from the operations limit. You can check the limit calculation in the pricing plans overview.

If a module outputs the DataSizeLimitExceededError with no error handling, the scenario ends with an error. Because the DataSizeLimitExceededError is a fatal error, Make immediately disables the scenario scheduling, regardless of the number of consecutive errors.

To fix the DataSizeLimitExceededError, consider purchasing extra operations or upgrading your organization's subscription plan.

A module outputs the DuplicateDataError when you send the same data to a module that doesn't allow duplicates. For example, when you try to create a new user in an app and the user's e-mail address has to be unique, but the e-mail address is used already. The module outputs the DuplicateDataError, because the e-mail address is registered with another user already.

If a module outputs the DuplicateDataError with no error handling, the scenario ends with an error. When your scenario finishes with an error for the number of consecutive errors in a row, Make disables the scheduling of your scenario.

If you get the DuplicateDataError in your scenario, you should review your scenario design. For example, if you are using a database, you could first check if the database record exists with a search module. Or with the tweet example, you could just ignore the error with the Ignore error handler.

A module outputs the IncompleteDataError when the module can get only part of the data from the third-party app.

For example, when you are uploading new photos to Google Photos and you have a scenario that downloads the photos at the same time. Make tries to download the photo that you are currently uploading. The photo file won't be complete and the Google Photos module will output the IncompleteDataError.

If a module outputs the IncompleteDataError with no error handling, the scenario ends with an error. Make pauses the scenario for 20 minutes and then runs the scenario again until the scenario succeeds or reaches the number of consecutive errors.

If you want to handle the IncompleteDataError, you can use the Break error handler.

A module outputs the InconsistencyError when an error happens during the scenario rollback. This error can occur when you make changes to a data store with two scenarios that run at the same time. If one scenario encounters an error and attempts to undo the changes in the rollback phase, but the other scenario already finished making changes, the changes cannot be safely undone and you get the InconsistencyError from the data store module in the first scenario.

For example, imagine two people making changes in the same part of a file. One of them saves changes before the other. What happens with the changes from the other person?

If a module outputs the InconsistencyError with no error handling, the scenario ends with an error. Because the InconsistencyError is a fatal error, Make immediately disables the scenario scheduling, regardless of the number of consecutive errors.

To fix the InconsistencyError, check your data and fix the data if necessary. If you are getting the InconsistencyError frequently, check the scenarios that use the database.

A module outputs the MaxFileSizeExceededError when you try to process a file that exceeds the maximum file size. The maximum file size differs based on your organization's subscription. You can check the maximum file sizes in the pricing plans overview.

For example, if you use the Google Drive > Move a file module in an organization with the Core plan to move a file larger than 100 MB, you would get the MaxFileSizeExceededError.

If a module outputs the MaxFileSizeExceededError with no error handling, the scenario ends with an error. When your scenario finishes with an error for the number of consecutive errors in a row, Make disables the scheduling of your scenario.

To fix the MaxFileSizeError, you have to either make the file smaller (compress or split the file) or upgrade your organization's subscription plan.

A module outputs the ModuleTimeoutError when the module is requesting or processing data for more than 40 seconds. For example, this error can happen when you are retrieving a large amount of data from the app or when the app has reduced availability.

If a module outputs the ModuleTimeoutError with no error handling, the scenario ends with an error. Make repeats the scenario run with increasing time delays.

To fix the ModuleTimeoutError with search modules, set the Limit in module settings to a lower number. To deal with reduced availability, check the article about fixing ConnectionError.

A module outputs the OperationsLimitExceededError when you run out of operations. Your operations limit is set with your organization's subscription. You can check your operations limit in the pricing plans overview.

If a module outputs the OperationsLimitExceededError, the scenario ends with an error. Because the OperationsLimitExceededError is a fatal error, Make immediately disables the scenario scheduling, regardless of the number of consecutive errors.

To fix the OperationsLimitExceededError, consider purchasing extra operations or upgrading your organization's subscription plan.

A module outputs the RateLimitError when you make too many requests over a time period to the app API. This error uses the HTTP 429 status code and follows the rate-limiting rules of the third party.

For example, the Make app modules output the RateLimitError when you reach the number of API calls per minute based on your subscription.

If a module outputs the RateLimitError with no error handling, the scenario ends with an error. Make pauses the scenario for 20 minutes and then runs the scenario again until the scenario succeeds.

To fix the RateLimitError, check the article about fixing the rate-limit errors.

A module outputs the RuntimeError when the error reported by the third-party app doesn't meet the criteria for any other error type. For example, you get the RuntimeError when you use up all your tokens with the OpenAI > Create a Completion module.

If a module outputs the RuntimeError with no error handling, the scenario ends with an error. When your scenario finishes with an error for the number of consecutive errors in a row, Make disables the scheduling of your scenario.

There's no general rule to fixing the RuntimeError. Check the error message in the scenario history or try to reproduce the error with the Make DevTool.

The overview of error handling can help you create your error handling strategy.