#6465 [Core feature] Task retry support in Flyte Connectors Issue created by rambrus ### Motivation: Why do you think this is important? We are migrating our Flyte workflows from Databricks Plugin to Databricks Connector. In Databricks Plugin, we mapped task failures to PhaseInfoRetryableFailure task phase (see Issue #5210) , which enabled us to use the Flyte task retry mechanism for Databricks tasks. Unfortunately, I could not find an equivalent task execution phase in Databricks Connector. I had a Slack conversation about this topic with @freezing-airport-6809 and @Future-Outlier and clarified that: • the retryable failures are supported in Flyte Plugins, because task execution states are mapped to flyteadmin's task states • in connector, task execution states are mapped to flyte propeller's task states • unfortunatly, there is no retryable failure task state in flyte propeller at the moment Could you please address the gap in the Flyte Connector architecture? It results in a loss of features for end users migrating from a plugin to a connector. ### Goal: What should the final outcome look like, ideally? The retryable failure state has been introduced to Flyte Propeller's task states. Connectors can map retryable failures to this state. ### Describe alternatives you've considered n/a ### Propose: Link/Inline OR Additional context https://flyte-org.slack.com/archives/CP2HDHKE1/p1747833003689039 ### Are you sure this issue hasn't been raised already? • Yes ### Have you read the Code of Conduct? • Yes flyteorg/flyte