My prefect agent was unreachable for several hours and a bunch of jobs got queued up behind it. When the agent restarted, it ran a bunch of duplicate jobs in a row. They’re idempotent so I think they’re okay, but I’m worried I’ll introduce a bug that depends on being the only job of its kind running at the same time, and in this kind of situation something bad could happen. Can I specify that a

Schedule

try and run, and if it fails expire the job after 60 seconds of trying?

Hi @Jason Prado! Are you on the enterprise license by chance? Because we rolled out automations where you can set flow-level SLAs to not run anymore if it’s been a certain amount of time after they failed.

Oh this is great. Thank you!