Channels
datahub-flyte
scipy-2023-workshop
flyte-school
agent-support-memverge
flyte-build
flyte-users-berlin
scipy-2023-sprint
auth
flyte-bazel
large-language-models
contribute
bioinformatics-computational-biology
great-content
in-flyte-conversations
flyte-on-gcp
show-and-tell
shameless-promotion
linkedin-flyte
random
deployment
hacktoberfest-2023
flyte-github
feature-discussions
linen-test
flytelab
flytekit-java
integrations
ray-on-flyte
conference-talks
release
flyte-ui-ux
workflow-building-ui-proj
writing-w-sfloris
jobs
hacktoberfest-2022
torch-elastic
flyte-console
engineeringlabs
helsing-flyte
flyte-documentation
konan-integration
databricks-integration
ray-integration
wg-gpu-types
flytekit
ecosystem-unionml
scipy-2022-sprint
announcements
ask-the-community
flyte-deployment
introductions
events
Powered by
#ask-the-community
Title
# ask-the-community
d
Derek Yu
09/27/2023, 7:08 AM
Hi, anyone know if there a way to set a task
timeout
across
retries, rather than
per
retry?
y
Yee
09/27/2023, 4:06 PM
no this is not currently possible.
you mean to keep a running counter of the time?
i don’t think i’ve heard that before.
d
Derek Yu
09/27/2023, 4:45 PM
yeah lets say 3 retries, if there's a timeout set to 1 hour, each retry attempt times out in 1 hour (so task doesn't time out until 3 hours). Vs, the task should timeout in 1 hour regardless of how many retries have been attempted
Post