Sometimes an error may occur during the execution of a scenario. This mostly happens if a service is unavailable due to failure or if a validation fails. Below we describe common errors that you may encounter.
Integromat distinguishes several basic error types. It reacts differently depending on the type of error that occurred.
Connection error is the most common error you may receive and Integromat can not avoid it. The problem arises when Integromat establishes connection to a third party service that is overloaded or temporarily unavailable (e.g. due to maintenance).
What happpens next if a connection error occurs depends on which module it was encountered. If the error occurs at the first module of a scenario, the execution of the scenario is terminated with a warning message. Integromat then repeatedly tries to run the scenario at increasing time intervals until it is succesfully completed. If these attempts fail, Integromat will stop the execution of the scenario.
If the connection error occurs at a module other than the first one, subsequent steps depend on whether you checked the Allow storing incomplete executionoption when setting the scenario. If this option is active, the execution of the scenario is moved to the Incomplete executions folder where Integromat tries at increasing intervals to complete the scenario. If all attempts fail, the execution will remain in the Incomplete executions folder and require manual intervention by the user. If the Allow storing incomplete executions option is not active, the execution of the scenario terminates with an error followed by a rollback phase.
By default, the increasing (delayed) intervals are set as follows: 10 minutes, 1 hour, 3 hours, 12 hours, 24 hours, Stop scenario execution.
Imagine, your scenario contains the Watch photos and videos module from the Picasa package. The Picasa service is, however, unavailable for 30 minutes due to maintenance. When Integromat starts the scenario, Picasa is unavailable. The scenario is stopped and started again after 10 minutes. As the service failure persists, Integromat is still unable to get information about new photos. Next run of the scenario starts after 1 hour. The Picasa service is already available and the scenario runs as expected.
A data error is generated when an item is incorrectly mapped and does not pass through a validation performed on the Integromat side or on the side of the third-party service being used.
If this error occurs, the rest of the scenario starting from the module that failed is moved to the Incomplete executions folder where you can troubleshoot the issue. However, the scenario is not stopped and continues to run according to schedule. To stop the execution of the scenario when Data error appears, enable the Sequential processing option in the scenario settings.
If you have not enabled the Allow storing incomplete executions option in the scenario settings, the execution of the scenario terminates with the error and a rollback is performed.
If your scenario contains the Create a tweet action from the Twitter package, the Twitter's 140-character limit for a tweet must not be exceeded. If you try to tweet more than 140 characters, the execution of the scenario will be terminated with DataError.
If Integromat tries to insert the same bundle twice into a service that does not allow duplicate data, a duplicate data error is generated. If this error occurs, Integromat proceeds in the same way as for the DataError.
A scenario containing the Create a tweet action from the Twitter package may terminate with this error if Integromat tries to insert the same tweet twice.
An Invalid Access Token Error occurs when Integromat can not access your account registered with a third-party service. This mostly happens when you revoke access rights of Integromat in the administration of a given service but related scenarios keep running according to schedule.
If this error occurs, the execution of a scenario is immediately stopped. The rest of the scenario starting from the module where the error occurred is moved to the Incomplete executions.
If a limit set by a given service is exceeded, a rate limit error is generated. If this error happens, Integromat proceeds in the same way as for the ConnectionError.
You will encounter this error, if you try to send more than 1000 tweets within 24 hours. If this happens, wait until this limitation is reset.
An incomplete Data Error occurs only with triggers. This error is generated if a trigger fails to download required data from a given service.
If a scenario terminates with the IncompleteDataError, its further behaviour will depend on the setting of the Max number of consecutive errors.
Imagine, you have a scenario with the Watch photos and videos trigger from the Picasa package. If the scenario is executed while you are uploading photos or videos to a selected album, Integromat might try to download a file that is just being uploaded to Picasa (E.g. a long video). If this happens, the scenario will terminate with the IncompleteDataError.
If any other error (not mentioned above) appears during scenario execution, it is reported as RunTimeError.
If a scenario terminates with the RuntimeError, its further behaviour will depend on the setting of the Max number of consecutive errors.
If this error appears in a scenario, the execution of the scenario is immediately stopped.
While executing a scenario, you may receive a warning informing you about a problem which, however, does not prevent the scenario from being succesfully completed.
A warning can appear, for example, when the maximum allowed file size is exceeded and the Enable data loss option is disabled.