From 604be4a67f93e8d8f0fc48b48a29ff17961f16bb Mon Sep 17 00:00:00 2001 From: Eduardo Apolinario <653394+eapolinario@users.noreply.github.com> Date: Tue, 8 Oct 2024 09:08:09 -0700 Subject: [PATCH] Add minimal version to failure nodes docs (#5812) Signed-off-by: Eduardo Apolinario Co-authored-by: Eduardo Apolinario --- docs/user_guide/development_lifecycle/failure_node.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/user_guide/development_lifecycle/failure_node.md b/docs/user_guide/development_lifecycle/failure_node.md index cd4c225d76..9bf7e2dd52 100644 --- a/docs/user_guide/development_lifecycle/failure_node.md +++ b/docs/user_guide/development_lifecycle/failure_node.md @@ -5,6 +5,11 @@ .. tags:: FailureNode, Intermediate ``` +:::{warning} +This feature is only available starting in Flyte 1.10.7. +::: + + The failure node feature enables you to designate a specific node to execute in the event of a failure within your workflow. For example, a workflow involves creating a cluster at the beginning, followed by the execution of tasks, and concludes with the deletion of the cluster once all tasks are completed. However, if any task within the workflow encounters an error, flyte will abort the entire workflow and won’t delete the cluster. This poses a challenge if you still need to clean up the cluster even in a task failure.