@ancient-wolf-19325 does flyte allow for retying/recovering inside a map task?

Flyte does support retries for tasks, including map tasks, but there are some limitations. According to Flyte's documentation, retries can be configured for both user and system errors. However, for map tasks, the retry behavior is managed at the platform level, and the

retries

field in the task annotation is not necessary for handling system errors, as these are managed by the platform’s configuration. Currently, Flyte's map tasks do not support

@dynamic

,

@eager

, or

@workflow

nodes, which limits the ability to recover or retry at a more granular level within a map task. This limitation is acknowledged in various discussions and issues within the Flyte community, and there are ongoing efforts to extend support for mapping over different Flyte node types, including dynamic and subworkflows, through the introduction of

ArrayNode

(source). Would you like more details on the current limitations or the upcoming

ArrayNode

feature? Sources: - Flyte Issue on MapTasks - Flyte's documentation 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.