Automatic retry of incomplete executions

{{product name}} checks the origin of every incomplete execution when it's created {{product name}} automatically retries incomplete executions that have been created because of ratelimiterror connectionerror moduletimeouterror and incomplete executions that were created with the break error handler docid\ hxe6n1fool691glswodgy with the automatic run completion enabled {{product name}} takes the following steps when {{product name}} retries incomplete executions {{product name}} schedules the incomplete execution retries {{product name}} retries the incomplete execution based on the incomplete execution retry result {{product name}} schedules another attempt or marks the incomplete execution resolved automatic retry scheduling {{product name}} schedules automatic retries with the exponential backoff docid\ le2snkujgl9uzqfm 0v3i schedule the backoff schedule prevents the situation when you would get the same error multiple times in a row for example, when you get the connectionerror because the app is unavailable, it might take some time until it's back {{product name}} spaces out the retry attempts to get a successful retry even at a later time after the original error error type retry schedule ratelimiterror connectionerror moduletimeouterror 1 minute (1 minute after the original {{scenario singular lowercase}} run) 10 minutes (11 minutes after the original {{scenario singular lowercase}} run ) 10 minutes (21 minutes after the original {{scenario singular lowercase}} run ) 30 minutes (51 minutes after the original {{scenario singular lowercase}} run ) 30 minutes (1 hour 21 minutes after the original {{scenario singular lowercase}} run ) 30 minutes (1 hour 51 minutes after the original {{scenario singular lowercase}} run ) 3 hours (4 hours 51 minutes after the original {{scenario singular lowercase}} run ) 3 hours (7 hours 51 minutes after the original {{scenario singular lowercase}} run ) error handled by the break error handler if you enable automatic {{scenario singular lowercase}} run completion in the error handler settings the default is maximum number of retry attempts 3 retry delay 15 minutes you can customize the defaults in the error handler settings other types of errors docid\ n4w0yaeop7a a4vfw ebp usually require changes in the incomplete execution and manage incomplete executions docid\ sfa 8jvnu5dmvrabnrser {{product name}} doesn't retry these error types automatically by default automatic retry processing after {{product name}} schedules the retries, {{product name}} runs the {{scenario singular lowercase}} again, starting with the module that caused the error for each {{scenario singular lowercase}} , there is a limit of 3 incomplete execution retries running in parallel if there are more incomplete executions scheduled from the same {{scenario singular lowercase}} , {{product name}} retries them in batches of 3 after the previous batch finishes in addition, the retry doesn't start when the original {{scenario singular lowercase}} is running already the 3 parallel retries limit applies to retries from the same {{scenario singular lowercase}} when {{product name}} retries incomplete executions from multiple {{scenario plural lowercase}} , then each of them has their own limit this limitation is to prevent your {{scenario plural lowercase}} from getting follow up rate limit errors if you are retrying a lot of incomplete executions at the same time for example you have a {{scenario singular lowercase}} that runs for 10 minutes every hour there was a disruption of a third party service for 5 hours the {{scenario singular lowercase}} now has 5 incomplete executions scheduled for automatic retry {{product name}} first waits until the original {{scenario singular lowercase}} finishes if it's running already this takes 10 minutes if the {{scenario singular lowercase}} started just now after the {{scenario singular lowercase}} finishes, {{product name}} retries the first 3 incomplete executions this takes an additional 10 minutes (20 in total) {{product name}} retries the remaining 2 incomplete executions after the previous batch finishes this takes another 10 minutes (30 in total) after another 30 minutes (1 hour in total), {{product name}} starts the {{scenario singular lowercase}} again according to the {{scenario singular lowercase}} schedule automatic retry result if a retry attempt succeeds, {{product name}} marks the incomplete execution as resolved and stops retrying if all of the retry attempts fail, {{product name}} marks the incomplete execution as unresolved you can then retry the incomplete execution when the app that caused the error is available again or you can resolve the incomplete execution manually