You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Timeouts in Flyte can be inconsistent due to how retries are handled for different types of errors. According to this discussion, node timeouts can sometimes lead to an "unknown" state, making it difficult to debug. Additionally, another discussion highlights that retries might not always behave as expected, especially with map tasks.
Would you like more detail on how to configure retries and handle timeouts in Flyte?
Describe the bug
Let's consider this task:
I'm seeing two attempts:
retries=10
Expected behavior
I would have expected either no retry or 10 retries.
Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: