Charles D
Charles D3mo ago

10 minutes run limit ?

Hello, I have a flow that includes a task that can take longer than 10 minutes. I notice my flow fails systematically silently at 10 minutes precisely, no matter what script it is in the flow. I have tried: - changing the Time window in seconds in concurrency at the flow level (to 800) - changing the Time window in seconds in concurrency at the script level (to 800 as well) - changing the timeout in runtime in the flow step (to 800) None of these seem to change anything. Am I missing something? Thanks
9 Replies
Charles D
Charles DOP3mo ago
I have simulated some usecases with some simple tasks that simply sleep. I seem that the issue is at the task level (a flow composed of a 300s wait and then a 700s wait will fail when the second task reaches 600s). I have both changed the Time window in seconds in concurrency at the script level (to 800 as well) and the timeout in runtime in the flow step (to 800) but it still fails at 600s. HELPPPPPP PLEASE
rubenf
rubenf3mo ago
writing HELP PLEASE is not gonna make us want to respond faster Now for your issue, are you using a sync endpoint ? I assume that you do, in which case you should set TIMEOUT_WAIT_RESULT as env variable to your servers to a number that is higher than 600
Charles D
Charles DOP3mo ago
It was meant to be a bit funny sorry. I should have specified it's on windmill cloud
rubenf
rubenf3mo ago
we do not support timeout of more than 10m on the multi-tenant cloud. But that's 600 executions for a single flow, is that what you really want ?
Charles D
Charles DOP3mo ago
basically, I am triggering an external task (a dbt task to be precise), and am waiting for it to complete - you have a better idea ? A while loop wouldn't change the 600 executions would it ? I have solved it temporarilly with retries, but it's not ideal as retries are not conditionnal.
rubenf
rubenf3mo ago
while loop would make it less expensive if you sleep in between it's just that you're gonna pay $0.6 per call
Charles D
Charles DOP3mo ago
While loop would be less expensive than the retries ? why ?
rubenf
rubenf3mo ago
because if you sleep in-between, the sleep is free
Charles D
Charles DOP3mo ago
Not the retry wait time ? (thanks for answering the questions and helping) Also, on the Cloud Team plan I thought we didn't pay by execution Ah gotcha 10k executions per month my bad.

Did you find this page helpful?