Hi all Using Prefect 1 x is it possible to have timeout expi

Question

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

Kevin Kho · Answer

Yes see <https docs prefect io orchestration concepts automations html|Automations> Specifically you can cancel a flow run if it is late by a certain amount of time using the Flow SLA

Joe Goldbeck · Answer

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

Kevin Kho · Answer

Yes because it relies on services not shipped with Server For Server your best bet is implementing something like <https github com PrefectHQ server issues 307|this> to cancel all of the extra runs

Joe Goldbeck · Answer

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

Joe Goldbeck · Answer

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 >

Kevin Kho · Answer

Yes that s right

Joe Goldbeck · Answer

Ok that s more sane slightly smiling face Sounds like a reason to update to 2 0 sooner rather than later Ty so much for the quick replies

Kevin Kho · Answer

Of course

Zanie · Answer

Ah actually that s not how `timeout seconds` works that s a timeout on flow run time

Zanie · Answer

There is no 2 x feature for flow scheduled start time enforcement yet

Zanie · Answer

It should be trivial to write a service though if you re not trying to have it as a configurable feature per flow

Joe Goldbeck · Answer

thinking face What do you mean by write a service

Joe Goldbeck · Answer

Like build something else outside of Prefect that polls the database and cleans up late runs or

Zanie · Answer

For v1 server I d add an image to the docker compose that queries for late runs in batches and updates their state yeah

Zanie · Answer

You could also subclass the agent to check differences between scheduled start time and the current time

Joe Goldbeck · Answer

Subclass the agent sounds like getting into internals

Joe Goldbeck · Answer

For the docker compose that sorta bumps the problem along a bit since then something needs to run and monitor those jobs stuck out tongue Tbh I m a bit surprised this isn t built in to the scheduler should have read the docs more carefully Appreciate the help