New RunLLM response generated: >>>*# Question* 👋 when status does flyte mark the task node when the pod associated with the node is pending (eg waiting to be scheduled by k8s)? Does that count towards the tasks timeout budget if set? code pointers would be amazing. Thank you ahead of time # Answer When a pod associated with a Flyte task node is in the pending state (e.g., waiting to be scheduled by Kubernetes), Flyte marks the task node with the status

Pending

. This pending time does count towards the task's timeout budget if set. According to this discussion, the

NodeActive

timeout includes the time spent queued (pending), while the

NodeExecution

timeout only includes the time spent running. Therefore, if you set a timeout for the task, the time the pod spends in the pending state will be included in the

NodeActive

timeout. For code pointers, you can refer to the FlytePropeller configuration for timeouts in the FlytePropeller config. Would you like more details on configuring these timeouts or any specific code examples? Sources: - FlytePropeller config - Flyte Discussion on Timeouts Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1723307515.075379 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.