From c3f7118cc7b54b06c45e55e0f23787087f1ceb8e Mon Sep 17 00:00:00 2001 From: Anirban Pal Date: Wed, 30 Oct 2024 23:41:47 +0700 Subject: [PATCH] updated line 152 tasks.rst --- docs/user_guide/concepts/main_concepts/tasks.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user_guide/concepts/main_concepts/tasks.rst b/docs/user_guide/concepts/main_concepts/tasks.rst index 0f2d5f30d6e..035957587ee 100644 --- a/docs/user_guide/concepts/main_concepts/tasks.rst +++ b/docs/user_guide/concepts/main_concepts/tasks.rst @@ -149,7 +149,7 @@ def my_task() -> None: ### Alternative Retry Behavior -Starting with RFC 3902, Flyte offers a simplified retry behavior where both system and user retries count towards a single retry budget defined in the task decorator. To enable this: +Starting with from 1.10.0, Flyte offers a simplified retry behavior where both system and user retries count towards a single retry budget defined in the task decorator. To enable this: 1. Set `configmap.core.propeller.node-config.ignore-retry-cause` to `true` in helm values 2. Define retries in the task decorator to set the total retry budget