Hello! I’m experiencing problems with subflows and...
# ask-community
k
Hello! I’m experiencing problems with subflows and
timeout_seconds.
I’ve put a timeout on both the parent and sub-flows, and the timout on the parents works nicely, leading to a ‘Timeout’ state after the specified time. The sub-flows just go on forever though. Anyone know what might be going wrong? Prefect version
2.7.8
r
what infra are you running on?
k
Kubernetes for Orion, agent and execution layer
r
whats your pod watch timeout set to on your infra block?
k
Copy code
pod_watch_timeout_seconds: 120
r
When you say the sub-flows just go on forever though are they expected to last longer?
k
And the parent flow has
@flow(timeout_seconds=2000)
Subflow has
@flow(timeout_seconds=3500)
Other way around sorry
r
can you increase pod_watch_timeout_seconds to above those values
k
That’s about pod creation timeouts though
r
from gh "The docstring is misleading - this timeout doesn't only apply to job startup, but also to job completion"
k
Number of seconds to watch for pod creation before timing out (default 60).
This is not correct?
You might be talking about:
job_watch_timeout_seconds
I have not set a
job_watch_timeout_seconds
, so it’s
None
in my setup
r
you sure its None in 2.7.8
k
Not 100% sure
r
I can see a bunch of fixes around this 2.8.3+
if you can I would try a move to latest as poss
k
Yes, I will try that. Any breaking changes with the Orion stuff or work pools vs work queues?
r
'Orion' is now 'Server'
but its not been removed yet
k
I’m now using the latest Prefect for everything in our setup. It still doesnt work
Or it might be the fact that the parent flow gets a timeout before the child
Will run an experiment now
👍 1
z
Can you share a minimal example?
(i.e. how are you calling the subflows)
k
Looks my problem went away when making the maximum cumelative subflow timeout less than the parent flows timeout 👍 Thanks for your help