Types of errors

within a {{scenario singular lowercase}} , you can have numerous modules and item mappings together, they create your {{scenario singular lowercase}} each of these elements can create an unexpected event an error {{product name}} categorizes errors based on their origin and their cause for example, the connectionerror happens when the app is unavailable because of maintenance or downtime on the third party side and {{product name}} can’t connect to the app servers when a module returns an error, {{product name}} highlights the module with the "caution" sign to check the error type, click the thought bubble above the module {{product name}} follows the standard error codes and their definitions note that it is possible that the third party may not fully comply with the standard accountvalidationerror a module outputs the accountvalidationerror when {{product name}} 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 https //en wikipedia org/wiki/list of http status codes if a module outputs the accountvalidationerror , the {{scenario singular lowercase}} ends with an error when your {{scenario singular lowercase}} finishes with an error for the overview of error handling docid 7 hehdtuu2xyys8 qurub in a row, {{product name}} disables the scheduling of your {{scenario singular lowercase}} it is not possible to handle the accountvalidationerror with an error handler, because the error happens during the initialization of the make docid\ m3kmlkl8455cs zz13ytb to fix the accountvalidationerror , review your credentials in the app and the connection in {{product name}} if necessary, create a new connection for the app if you are getting the accountvalidationerror frequently, contact our support https //www make com/en/ticket bundlevalidationerror 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, {{product name}} 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 https //en wikipedia org/wiki/list of http status codes 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 singular lowercase}} ends with an error when your {{scenario singular lowercase}} finishes with an error for the overview of error handling docid 7 hehdtuu2xyys8 qurub in a row, {{product name}} disables the scheduling of your {{scenario singular lowercase}} 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 singular lowercase}} check out the article about fixing missing data errors docid\ ei26zlhgxbmjk7woiqfw connectionerror 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 https //en wikipedia org/wiki/list of http status codes the default handling of the connectionerror depends on the following attributes {{scenario singular lowercase}} scheduling enabling of the incomplete executions incomplete executions disabled incomplete executions enabled scheduled {{scenario singular lowercase}} {{product name}} pauses the scheduling of the scenario for 20 minutes {{product name}} doesn't rerun the scenario {{product name}} pauses the scheduling of the scenario for 20 minutes {{product name}} retries the incomplete execution with the incomplete execution exponential backoff docid\ le2snkujgl9uzqfm 0v3i instant {{scenario singular lowercase}} {{product name}} reruns the incomplete execution with the {{scenario singular lowercase}} exponential backoff docid\ le2snkujgl9uzqfm 0v3i {{product name}} retries the incomplete execution with the incomplete execution exponential backoff docid\ le2snkujgl9uzqfm 0v3i to fix the connectionerror , check the fixing connection errors connectionerrors docid\ bbfjxepacbq4bweghxszy dataerror 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 date and time functions docid 1kv1ib5q50i0slbc7g2pz function if a module outputs the dataerror with no error handling, the {{scenario singular lowercase}} ends with an error when your {{scenario singular lowercase}} finishes with an error for the overview of error handling docid 7 hehdtuu2xyys8 qurub in a row, {{product name}} disables the scheduling of your {{scenario singular lowercase}} 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 error handler docid\ wr8aaeme2ptfar38vxd3p and ignore error handler docid\ xzfc2uhei4kmsmhydbnmp error handlers datasizelimitexceedederror a module outputs the datasizelimitexceedederror when you run out of data transfer quota your data transfer limit is calculated from the credits limit if a module outputs the datasizelimitexceedederror with no error handling, the {{scenario singular lowercase}} ends with an error because the datasizelimitexceedederror is a fatal error, {{product name}} immediately disables the {{scenario singular lowercase}} scheduling, regardless of the overview of error handling docid 7 hehdtuu2xyys8 qurub to fix the datasizelimitexceedederror , consider buying extra credits docid 2zcwidbk uamtp2x2 7kj or upgrading your organization's subscription plan duplicatedataerror 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 singular lowercase}} ends with an error when your {{scenario singular lowercase}} finishes with an error for the overview of error handling docid 7 hehdtuu2xyys8 qurub in a row, {{product name}} disables the scheduling of your {{scenario singular lowercase}} if you get the duplicatedataerror in your {{scenario singular lowercase}} , you should review your {{scenario singular lowercase}} 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 email example, you could just ignore the error with the ignore error handler docid\ xzfc2uhei4kmsmhydbnmp incompletedataerror 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 singular lowercase}} that downloads the photos at the same time {{product name}} 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 singular lowercase}} ends with an error {{product name}} pauses the scenario for 20 minutes and then runs the {{scenario singular lowercase}} again until the {{scenario singular lowercase}} succeeds or reaches the overview of error handling docid 7 hehdtuu2xyys8 qurub if you want to handle the incompletedataerror , you can use the error handler docid\ hxe6n1fool691glswodgy inconsistencyerror a module outputs the inconsistencyerror when an error happens during the {{scenario singular lowercase}} rollback docid\ m3kmlkl8455cs zz13ytb this error can occur when you make changes to a data store with two {{scenario plural lowercase}} that run at the same time if one {{scenario singular lowercase}} encounters an error and attempts to undo the changes in the rollback phase, but the other {{scenario singular lowercase}} already finished making changes, the changes cannot be safely undone and you get the inconsistencyerror from the data store module in the first {{scenario singular lowercase}} 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 singular lowercase}} ends with an error because the inconsistencyerror is a fatal error, {{product name}} immediately disables the {{scenario singular lowercase}} scheduling, regardless of the overview of error handling docid 7 hehdtuu2xyys8 qurub to fix the inconsistencyerror , check your data and fix the data if necessary if you are getting the inconsistencyerror frequently, check the {{scenario plural lowercase}} that use the database maxfilesizeexceedederror 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 {{product name}} pricing 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 singular lowercase}} ends with an error when your {{scenario singular lowercase}} finishes with an error for the overview of error handling docid 7 hehdtuu2xyys8 qurub in a row, {{product name}} disables the scheduling of your {{scenario singular lowercase}} to fix the maxfilesizeerror , you have to either make the file smaller (compress or split the file) or upgrade your organization's subscription plan moduletimeouterror 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 the default handling of the moduletimeouterror depends on the following attributes {{scenario singular lowercase}} scheduling enabling of the incomplete executions incomplete executions disabled incomplete executions enabled scheduled {{scenario singular lowercase}} {{product name}} pauses the scheduling of the scenario for 20 minutes {{product name}} doesn't rerun the scenario {{product name}} pauses the scheduling of the scenario for 20 minutes {{product name}} retries the incomplete execution with the incomplete execution exponential backoff docid\ le2snkujgl9uzqfm 0v3i instant {{scenario singular lowercase}} {{product name}} reruns the incomplete execution with the {{scenario singular lowercase}} exponential backoff docid\ le2snkujgl9uzqfm 0v3i {{product name}} retries the incomplete execution with the incomplete execution exponential backoff docid\ le2snkujgl9uzqfm 0v3i to fix the moduletimeouterror with search modules, set the limit in module settings to a lower number to deal with reduced availability, check the fixing connection errors connectionerror docid\ bbfjxepacbq4bweghxszy operationslimitexceedederror a module outputs the operationslimitexceedederror when you run out of credits your credit limit is set with your organization's subscription you can check your credit limit in pricing if a module outputs the operationslimitexceedederror , the {{scenario singular lowercase}} ends with an error because the operationslimitexceedederror is a fatal error, {{product name}} immediately disables the {{scenario singular lowercase}} scheduling, regardless of the overview of error handling docid 7 hehdtuu2xyys8 qurub to fix the operationslimitexceedederror , consider buying extra credits docid 2zcwidbk uamtp2x2 7kj or upgrading your organization's subscription plan ratelimiterror 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 https //en wikipedia org/wiki/list of http status codes and follows the rate limiting https //en wikipedia org/wiki/rate limiting rules of the third party for example, the make app docid\ g7vz7fysaoicjddxzcncz modules output the ratelimiterror when you reach the number of api calls per minute based on your subscription the default handling of the ratelimiterror depends on the following attributes {{scenario singular lowercase}} scheduling enabling of the incomplete executions incomplete executions disabled incomplete executions enabled scheduled {{scenario singular lowercase}} {{product name}} pauses the scheduling of the scenario for 20 minutes {{product name}} doesn't rerun the scenario {{product name}} pauses the scheduling of the scenario for 20 minutes {{product name}} retries the incomplete execution with the incomplete execution exponential backoff docid\ le2snkujgl9uzqfm 0v3i instant {{scenario singular lowercase}} {{product name}} reruns the incomplete execution with the {{scenario singular lowercase}} exponential backoff docid\ le2snkujgl9uzqfm 0v3i {{product name}} retries the incomplete execution with the incomplete execution exponential backoff docid\ le2snkujgl9uzqfm 0v3i to fix the ratelimiterror , check the fixing rate limit errors docid\ oxgtalgvur0yzkn ux9wk runtimeerror 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 singular lowercase}} ends with an error when your {{scenario singular lowercase}} finishes with an error for the overview of error handling docid 7 hehdtuu2xyys8 qurub in a row, {{product name}} disables the scheduling of your {{scenario singular lowercase}} there's no general rule to fixing the runtimeerror check the error message in the {{scenario singular lowercase}} history or try to reproduce the error with the make devtool docid\ bchjzzddem 1pyfex4npc the overview of error handling docid 7 hehdtuu2xyys8 qurub can help you create your error handling strategy