Is there a good way to tell the reason for a work queue going into the

unhealthy

state? It looks like one of ours did so right at 9am this morning. Our infrastructure is all up and healthy, so I'm not sure why the work queue would report

unhealthy

Hi Scott! are there any late runs in the queue? This will cause the queue to report unhealthy

Yes there are 50+ late runs! I assumed they were late because of the unhealthy queue though.

do you have a concurrency limit set?

I did try restarting before posting here unfortunately :/

Could you check if your work pool is paused? It's the toggle on the main work pool page (below is an

active

example of the toggle):

^^^ that was the cause, thank you!

The primary ways for a work pool to get paused are: • the UI toggle here •

prefect work-pool pause ...

via the CLI • An automation is configured to pause a work pool based on certain triggers The default state of a work pool is always active. There shouldn't be anything else behind the scenes that is switching this to pause automatically

interesting, thanks for the info. Seems like it had to have been a user via CLI or the toggle

thanks jake for the help!