Automatic retry of incomplete executions

checks the origin of every incomplete execution when it's created automatically retries incomplete executions that have been created because of ratelimiterror connectionerror moduletimeouterror and incomplete executions that were created with the docid\ hxe6n1fool691glswodgy with the automatic run completion enabled takes the following steps when retries incomplete executions schedules the incomplete execution retries retries the incomplete execution based on the incomplete execution retry result schedules another attempt or marks the incomplete execution resolved automatic retry scheduling schedules automatic retries with the 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 spaces out the retry attempts to get a successful retry even at a later time after the original error true 232 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type other docid\ n4w0yaeop7a a4vfw ebp usually require changes in the incomplete execution and docid\ sfa 8jvnu5dmvrabnrser doesn't retry these error types automatically by default automatic retry processing after schedules the retries, runs the again, starting with the module that caused the error for each , there is a limit of 3 incomplete execution retries running in parallel if there are more incomplete executions scheduled from the same , retries them in batches of 3 after the previous batch finishes in addition, the retry doesn't start when the original is running already the 3 parallel retries limit applies to retries from the same when retries incomplete executions from multiple , then each of them has their own limit this limitation is to prevent your 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 that runs for 10 minutes every hour there was a disruption of a third party service for 5 hours the now has 5 incomplete executions scheduled for automatic retry first waits until the original finishes if it's running already this takes 10 minutes if the started just now after the finishes, retries the first 3 incomplete executions this takes an additional 10 minutes (20 in total) 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), starts the again according to the schedule automatic retry result if a retry attempt succeeds, marks the incomplete execution as resolved and stops retrying if all of the retry attempts fail, 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