Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Flyte provides two options for the `failure_policy` in workflows:

1. *FAIL_IMMEDIATELY*: The entire workflow execution fails as soon as a component node fails.
2. *FAIL_AFTER_EXECUTABLE_NODES_COMPLETE*: The workflow continues to execute any remaining runnable nodes after a component node fails.

These options are part of the `WorkflowFailurePolicy` class in Flytekit. Would you like more details on how to implement these policies?

Sources:
- <https://docs.flyte.org/en/latest/api/flytekit/generated/flytekit.WorkflowFailurePolicy.html#rtd-footer-container|Flytekit WorkflowFailurePolicy>
- <https://github.com/flyteorg/flytekit/blob/master/flytekit/core/workflow.py|Flytekit GitHub WorkflowFailurePolicy> :+1: 0 button :-1: 0 button 💡 *Hint:* Mention @runllm in the thread for followups.