Introduction to errors and warnings

when an automation does not behave as expected, reports the issue as either a warning or an error, preventing your scenario from running errors and warnings can occur due to several reasons including connection issues, invalid mapping, api errors, etc errors in errors indicate that your encountered an unexpected event that was not handled by an as a result, you should review the to identify and resolve the issue how to identify errors a module will return an error when it receives invalid data from previous modules or from the app itself when you open your in the editor, highlights the module that produced the error with an alert sign to view the error type, click the alert sign displayed above the module when you click the caution sign, you can check the bundle that caused the error in the module shows the error type and the error message different options to resolve this error the purple action button opens the help center in a pop up window when a module outputs an error, stops the current run and initiates a rollback during this phase, attempts to revert any changes made before the error occurred, restoring the system to the state it was in prior to the execution if a encounters errors across multiple consecutive runs, automatically disables the 's schedule disabling the prevents repeated failed executions, allowing you time to investigate and resolve the issue while avoiding unnecessary consumption of operations what causes errors in make the following are the most common reasons that can cause a module to return an error data handling these errors occur when there are issues with the data transferred between modules an error may arise if the data is incorrect or not in the right format make ensures that only valid data is processed in a scenario error examples bundle validation errors docid\ slue xtn4t2rhh5i yjp8 data error docid\ slue xtn4t2rhh5i yjp8 duplicate data error docid\ slue xtn4t2rhh5i yjp8 incomplete data error docid\ slue xtn4t2rhh5i yjp8 organization limits as per your plan, you have resources allotted for your organization exceeding these resource limits in your plan will prevent your scenarios from running error examples max file size exceeded error docid\ slue xtn4t2rhh5i yjp8 operations limit exceeded error docid\ slue xtn4t2rhh5i yjp8 data size limit exceeded error docid\ slue xtn4t2rhh5i yjp8 api related these errors can occur due to the changes to apis, authentication or authorization settings an error may occur due to changes in the connection, such as expired api keys, unavailable apis, or revoked access after team or permission changes error examples account validation error docid\ slue xtn4t2rhh5i yjp8 module timeout error docid\ slue xtn4t2rhh5i yjp8 connection error docid\ slue xtn4t2rhh5i yjp8 rate limit error docid\ slue xtn4t2rhh5i yjp8 runtime error docid\ slue xtn4t2rhh5i yjp8 how errors are categorized classifies errors based on two primary factors, their origin and their underlying cause example a connectionerror typically occurs when a third party service is having an issue or incident in this case, the origin is the external server, and the cause is the inability to establish a connection error notifications when errors are not handled by any error handler, sends you an email notification also sends out a notification when your gets disabled because of repeated errors you can learn more about email notifications and their settings here docid\ w6mie5w1v2tvbemgxp s warnings in warnings alert you that there was an issue during the run, but not as serious as an error also, can have a warning status if errors are successfully handled by your configured error handlers or when a module in a returns a warning, your keeps running and stays enabled a warning doesn't disable the scheduling of your and warnings don't count into the number of consecutive errors docid 7 hehdtuu2xyys8 qurub but it's a good idea to check the scenario execution history docid 9z2xnh lyy62cfahjfhj5 to view the cause of the warning a warning can also be the result of handling an error with the retry error handler docid\ cptwi8yi45zl3m5slzjnv with the warning informs you that the retry error handler created an incomplete execution docid 6zznn7v35herrcjfccp9q of your when a module returns a warning, highlights the module with a yellow caution sign to check the warning, click the caution sign displayed above the module when you use , you will see a warning when the error handler activates in the example above, the retry error handler docid\ cptwi8yi45zl3m5slzjnv handled the bundlevalidationerror docid\ n4w0yaeop7a a4vfw ebp the error handler activation turned the original error into a warning the following are the most common that cause a module to return a warning when a module outputs an error, but you have enabled the storing of incomplete executions docid\ evar6qlowv4yyuneyv 00 in the settings when the data store used in a reaches its capacity limit when the execution time of a run exceeds the duration limit of your subscription