Sometimes an error can occur during the execution of a scenarioA specific connection between applications in which data can be transferred. Two types of scenarios: active/inactive.. This mostly happens if a service is unavailable due to a failure to connect to a service or if validation fails. Below we describe the common errors that you may encounter.
Boost.space IntegratorPart of the Boost.space system, where you can create your connections and automate your processes. distinguishes between several basic error types. It will react differently depending upon the type of error that occurred.
ConnectionError
The connectionUnique, active service acces point to a network. There are different types of connections (API key, Oauth…). error is one of the most common errors usually caused by the unavailability of the third-party service for various reasons (overloading, maintenance, outage, etc.). The default handling of this error depends on which module it was encountered on:
- If the error occurs on the first module, the execution of the scenario is terminated with a warning message. Boost.space Integrator then repeatedly attempts to rerun the scenario at increasing time intervals. If all attempts fail, Boost.space Integrator deactivates the scenario.
- If the connection error occurs on another module than the first one, the subsequent steps depend on the Allow storing incomplete execution option in the scenario advanced settings:
- If this option is enabled, the execution of the scenario is moved to the Incomplete executions folder where Boost.space Integrator repeatedly attempts to rerun the scenario at increasing time intervals. If all attempts fail, the execution will remain in the Incomplete executionsSometimes Boost.space Integrator cannot successfully finalize a scenario execution due to an error. Boost.space Integrator stores incomplete executions in a folder named Incomplete Executions. Each stored incomplete execution can be resolved either manually or automatically. folder awaiting manual resolution by the user.
- If the option is disabled, the execution of the scenario ends with an error followed by a rollback phaseRollback is a phase that occurs when there is an error during the operation or commit phase on any module. The scenario execution stops the operation or commit phase and starts the rollback phase, reversing all changes in data.. Boost.space Integrator then repeatedly attempts to rerun the scenario at increasing time intervals. If all attempts fail, Boost.space Integrator deactivates the scenario.
The algorithm of multiplicatively increasing time intervals between attempts when an error occurs is known as Exponential backoff. The increasing time intervals are set as follows:
- 1 minute
- 2 minutes
- 5 minutes
- 10 minutes
- 1 hour
- 3 hours
- 12 hour
- 24 hour
![[Note]](https://docs.boost.space/wp-content/themes/bsdocs/docs-parser/HTML/css/image/note.png) |
Note |
|---|---|
| The main reason for employing the increasing time intervals in Boost.space Integrator is to prevent frequently executed scenariosA specific connection between applications in which data can be transferred. Two types of scenarios: active/inactive. to consume operationsOperations are tasks in integration scenarios, similar to "operations" in Make.com. Each action, like reading or updating a record, counts as one operation. They’re essential for data syncing between apps and reset monthly. Going over the limit pauses syncing until you add more or upgrade your plan. on repeatedly failing attempts. |
Example
Imagine, your scenario contains the Google Photos trigger Watch photos and videos. However, the Google Photos service is unavailable for 30 minutes due to maintenance. As you can guess when Boost.space Integrator starts the scenario, Google Photos is unable to retrieve new photos or videos. The scenario stops and tries again in 10 minutes. As the service continues to be unavailable within this time frame, Boost.space Integrator is still unable to get information about new photos. The next run of the scenario is scheduled in 1 hour. The Google Photos service is available again within this time and the scenario runs as expected.
DataError
A data error is generated when an item is incorrectly mapped and does not pass the validation performed on the Boost.space Integrator side or on the side of the third-party service being used.
If this error occurs, the scenario, up to where the module failed, is moved to the Incomplete executions folder where you can troubleshoot the issue. However, the scenario does not stop and continues to run according to its schedule. To stop the execution of the scenario when a 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.
Example
If your scenario contains the Twitter action Create a tweet, Twitter’s 280-character limit for a tweet cannot be exceeded. If you try to tweet more than 280 characters, the execution of the scenario will terminate with a data error.
DuplicateDataError
If Boost.space Integrator tries to insert the same bundleA bundle is a chunk of data and the basic unit for use with modules. A bundle consists of items, similar to how a bag may contain separate, individual items. twice into a service that does not allow duplicate data, a duplicate data error is generated. If this error occurs, Boost.space Integrator proceeds in the same way as it does for the data error.
Example
A scenario containing the Twitter action, Create a tweet will terminate with this error if Boost.space Integrator tries to insert the same tweet twice.
InvalidAccessTokenError
An invalid access tokenThe API token is a multi-digit code that allows a user to authenticate with cloud applications. error occurs when Boost.space Integrator cannot access your account registered with a third-party service. This mostly happens when you revoke access rights for Boost.space Integrator 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 stopped immediately. The rest of the scenario starting from the module where the error occurred is moved to the Incomplete executions.
RateLimitError
If a limit set by a given service is exceeded, a rate limit error is generated. If this error happens, Boost.space Integrator proceeds in the same way as it does for the ConnectionError.
IncompleteDataError
An incomplete data error occurs only with triggersEvery scenario has a trigger, an event that starts your scenario. A scenario must have a trigger. There can only be one trigger for each scenario. When you create a new scenario, the first module you choose is your trigger for that scenario. Create a trigger by clicking on the empty module of a newly created scenario or moving the.... This error is generated if a triggerEvery scenario has a trigger, an event that starts your scenario. A scenario must have a trigger. There can only be one trigger for each scenario. When you create a new scenario, the first module you choose is your trigger for that scenario. Create a trigger by clicking on the empty module of a newly created scenario or moving the... fails to download required data from a given service.
If a scenario terminates with the IncompleteDataError, its further behavior will depend on its setting of Max number of consecutive errors.
Example
Imagine, you have a scenario with the Google Photos trigger Watch photos and videos. If the scenario is executed while you are uploading photos or videos to a selected album, Boost.space Integrator might try to download a file that is just being uploaded to Google Photos (e.g. a long video). If this happens, the scenario will terminate with the IncompleteDataError.
RuntimeError
If any other error (not mentioned above) appears during scenario execution, it is reported as a RunTimeError.
If a scenario terminates with the RuntimeError, its further behavior will depend on its setting of Max number of consecutive errors.
|
Note |
|---|---|
| If a scenario starts with an instant trigger, the setting of Max number of consecutive errors is ignored and the scenario is deactivated immediately once the first error has occurred. |
InconsistencyError
If any error described above occurs during the commit or rollback phase, a scenario will terminate with an Inconsistency Error.
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. However, it does not prevent the scenario from being successfully completed.
For example, a warning can appear when the maximum allowed file size is exceeded and the Enable data loss option is disabled.