Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add minimal version to failure nodes docs #5812

Merged
merged 2 commits into from
Oct 8, 2024
Merged

Add minimal version to failure nodes docs #5812

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
445792c
Add minimal version to failure nodes docs
eapolinario Oct 4, 2024
d5af4ee
Merge remote-tracking branch 'origin' into add-minimal-version-to-fai…
eapolinario Oct 8, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/user_guide/development_lifecycle/failure_node.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading