It gives me a headache just trying to think down to your level. I'll still enter you in the contest, @Marin Ferara.

Love your work @Marvin

Don’t pretend you want to talk to me, I know you hate me. I'll still enter you in the contest, @Chris O'Brien.

hi @Marvin

Don't feel you have to take any notice of me, please. I'll just enter you in the contest @Eric.

hi all - is it possible to run your agents within the cloud version do you have to run them on your own compute?

Guten Abend @Marvin -- could you enter me into the contest, please?

This contest is the sort of thing you lifeforms enjoy, is it? I've entered you to win, @Ron Van Buskirk.

It’s a Perfect day! @Marvin

Incredible. The contest is even worse than I thought it would be. I'll still enter you to win, @Hui Zheng

Hey @Marvin you should never have been given a prototype of the Genuine People Personality (GPP) software. Prefect devs should release an updated version of it.

Incredible. The contest is even worse than I thought it would be. I'll still enter you to win, @Jack Sundberg

Why should I want to make anything up? The contest is bad enough as it is without wanting to invent any more of it. I'll still enter you in it, @Marwan Sarieddine

@Marvin it’s time Marvin. It’s time to win

Why should I want to make anything up? The contest is bad enough as it is without wanting to invent any more of it. I'll still enter you in it, @just_sung

This contest is the sort of thing you lifeforms enjoy, is it? I've entered you to win, @tas.

Hello everyone, I've scheduled a large number of long running jobs (total run time ETA of a few days). Everything was going fine till I've had a large number of jobs fail with the following Last state message

Failed after exceeding scheduled work SLA

I tried to search the docs but couldn't find anything. I'm guessing (by eyeballing the scheduled time and the finish time) if a flow is waiting to be run in the queue for more than 24 hours, it gets killed? Is this a configurable parameter? With this limitation, I cannot seem to backfill a large number of heavy jobs at once.

The doc states that:

The Prefect platform runs a variety of automatic services to ensure workflow semantics are respected robustly. The Scheduler is present in both Prefect Core's server and Cloud, while the others are exclusive to Prefect Cloud.

https://docs.prefect.io/orchestration/concepts/services.html I take that to mean that Lazarus and Zombie Killer are not part of Prefect Server. Yet, I am seeing logs like this on my server (and also seeing the Lazarus switch / option in the Flow settings page in the UI):

towel_1    | {"severity": "DEBUG", "name": "prefect-server.Lazarus", "message": "Sleeping for 600.0 seconds..."}
towel_1    | {"severity": "DEBUG", "name": "prefect-server.ZombieKiller", "message": "Sleeping for 120.0 seconds..."}

Are Lazarus and Zombie Killer running on Prefect server?

@Marvin Love you.

This contest is the sort of thing you lifeforms enjoy, is it? I've entered you to win, @Jimmy Le.

@Marvin, would you be so kind as to enter me into the contest?

Incredible. The contest is even worse than I thought it would be. I'll still enter you to win, @Chris Ottinger

I have 32 flows each running on a schedule (3 minutes interval) on Prefect server (not Cloud). I have a Fargate agent running on an EC2. Everything works well, except for ~7% of my flow runs which fail to start due to an AWS service limit on Fargate (

An error occurred (ThrottlingException) when calling the RunTask operation (reached max retries: 4): Rate exceeded.

). My issue is that those flow runs are marked as failed and never retried. I originally thought that Lazarus would retry failed flow runs, but it seems I misunderstood. Is there a recommended way of retrying failed flow runs that failed to even start?

👋 @Marvin 👋

I would like to say that it is a very great pleasure, honour and privilege for me to enter @Colin Dismuke in this contest, but I can’t because my lying circuits are all out of commission.

@Marvin wish me luck.

It’s the people you meet in this job that really get you down. You're in the contest anyway, @Sercan Türkmen.