https://prefect.io
Join Slack
Hi all: Using Prefect 1.x, is it possible to have timeout/expiration for late flow runs? We run an ...
# ask-community
j
Hi all: Using Prefect 1.x, is it possible to have timeout/expiration for late flow runs? We run an export job every 15 minutes, so if our agent goes down, these can accumulate rather quickly. When the agent comes back up, we do not want to go back and run all the missed scheduled runs, we just want to pick back up from wherever it is.
k
Yes see Automations. Specifically you can cancel a flow run if it is late by a certain amount of time using the Flow SLA
j
Thanks! Is this kind of ability Cloud only? e.g. if we are running our own Server, we could not clear these out except by hand?
k
Yes because it relies on services not shipped with Server. For Server, your best bet is implementing something like this to cancel all of the extra runs
j
I see ty! I am surprised there is no simple way to do this, but I should have done better research, hah. One my quick q if you have the time
in Prefect 2, I see 
timeout_seconds
in Flow. Would that expire a flow if it hasn’t been started running by timeout_seconds after the scheduled start time? https://orion-docs.prefect.io/api-ref/prefect/flows/
k
Yes that’s right
j
Ok that’s more sane 🙂. Sounds like a reason to update to 2.0 sooner rather than later. Ty so much for the quick replies!
k
Of course!
z
Ah actually that’s not how 
timeout_seconds
works — that’s a timeout on flow run time
There is no 2.x feature for “flow scheduled start time” enforcement yet
🙁 1
It should be trivial to write a service though if you’re not trying to have it as a configurable feature per-flow
j
🤔 What do you mean by “write a service”?
Like build something else outside of Prefect that polls the database and cleans up late runs, or…?
z
For v1 server I’d add an image to the docker-compose that queries for late runs in batches and updates their state, yeah
You could also subclass the agent to check differences between scheduled start time and the current time
🤔 1
j
Subclass the agent sounds like getting into internals?
For the docker-compose, that sorta bumps the problem along a bit since then something needs to run and monitor those jobs 😛. Tbh I’m a bit surprised this isn’t built-in to the scheduler – should have read the docs more carefully. Appreciate the help!
7 Views
Open in Slack
PreviousNext
Powered by

Prefect Community

Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Powered by