<#6567 [Core feature] Add support for Flyte Propel...
# flyte-github
c
#6567 [Core feature] Add support for Flyte Propeller Back Off Issue created by Sovietaced ### Motivation: Why do you think this is important? Right now when Flyte Propeller encounters a system error it seems to write the error to the workflow status, which immediately enqueues the workflow. This causes Flyte Propeller to evaluate workflows encountering errors in a relatively tight loop. In some cases 30x system retries are performed within a second until the retry limit is reached. There should be some way to configure an exponential backoff for reevaluating workflows after system errors. This would likely fix race conditions like #6556 ### Goal: What should the final outcome look like, ideally? I would like workflows encountering errors to be reevaluated according to some sort of configurable back off mechanism ### Describe alternatives you've considered None ### Propose: Link/Inline OR Additional context No response ### Are you sure this issue hasn't been raised already? • Yes ### Have you read the Code of Conduct? • Yes flyteorg/flyte