Sometimes, an error can occur during when a scenario is executed. The below are the common type of users may encounter. There are several basic error types within Alaya Connector.
This is one of the most common errors and is usually caused by third-party service is unavailable due to maintenance or outage. The default handling of this error depends on the following situations:
- If the error occurs on the first module, scenario termination will be terminated with a warning message. Alaya Connector will repeatedly attempt to rerun the scenario at increasing time intervals. If all attempts fail, the scenario will de deactivated.
- If the connection error occurs on another module, depending on the user's advanced scenario settings, one of the following will occur:
- If this option is enabled, the execution of the scenario is moved to the "Incomplete Executions" folder. Alaya Connector will repeatedly attempt to rerun the scenario at increasing time intervals. If all attempts fail, the scenario will de deactivated. Manual resolution from the user will be required.
- If the option is disabled, an error will display and is followed by a rollback phase. Alaya Connector will repeatedly attempt to rerun the scenario at increasing time intervals. If all attempts fail, the scenario will de deactivated.
What are the frequency to "Increasing time intervals"?
The increasing time intervals are set as follows:
- 10 minutes
- 1 hour
- 3 hours
- 12 hours
- 24 hours
A data error is generated when an item is incorrectly mapped and does not pass the validation performed on either Alaya Connector or on the third-party service.
If this error occurs, right up to where the module failed, the scenario will be moved to the "Incomplete executions" folder, where users can manually troubleshoot the issue. Please note that the scenario will continue to run according to its schedule. To stop a scenario from executing when a data error occurs, enable the "Sequential processing" option under the scenario's settings. If you have not enabled the "Allow storing incomplete executions" option under the scenario's settings, the scenario will stop executing and a rollback will be performed.
Duplicate Data Error
A duplicate data error is generated when the same bundle is inserted twice into a service that does not allow duplicate data. Alaya Connector will process this error the same as it will do for the Data Error.
Invalid Access Token Error
An invalid access token error occurs when Alaya Connector fails to access the user's registered account on a third-party service. You may resolve this by checking to see if you have revoked Alaya Connector's access rights on the third-party service, or if you may have changed your password. If this error occurs, the execution of a scenario is stopped immediately. The rest of the scenario from the point where the error has taken place is then moved to the "Incomplete executions" folder.
Rate Limit Error
A rate limit error is generated when a limit set by a third-party service is exceeded. Alaya Connector will process this error the same as it will do for the Connection Error.
Incomplete Data Error
An incomplete data error occurs only with triggers, when a trigger fails to download required data from a third-party service. If a scenario is stopped from its execution due to this behaviour, users should check the settings on the maximum number of consecutive errors for more information.
Run time error
A RunTimeError is any other error that appears during scenario execution. When a scenario terminates with this type of error, users will need to check the settings, especially the maximum number of consecutive errors, for more information. If a scenario starts with an instant trigger, settings pertaining to the maximum number of consecutive errors will be ignored and the scenario is deactivated immediately as soon as the first error has occurred.
If any error described above occurs during the commit or rollback phase, the scenario will terminate with an "Inconsistency Error". The scenario will be stopped immediately. Refer to this article for more information on the different types of error handling directives.
Sometimes, users will receive a Warning message when a scenario runs into an issue during execution. This does not always mean that the scenario cannot be successfully completed. Be sure to check your results and settings in the event that it was not successfully completed.