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

Question

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`

Jamie Zieziula · Answer

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

skrawczyk · Answer

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

skrawczyk · Answer

I provided more context here <https prefect community slack com archives CL09KU1K7 p1690385566712669|https prefect community slack com archives CL09KU1K7 p1690385566712669>

Jamie Zieziula · Answer

do you have a concurrency limit set

Jamie Zieziula · Answer

oop nevermind i see that you dont

Jamie Zieziula · Answer

can you restart the worker and see if that helps

skrawczyk · Answer

I did try restarting before posting here unfortunately

Jake Kaplan · Answer

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

skrawczyk · Answer

^^^ that was the cause thank you

skrawczyk · Answer

Are you aware of any reason why that would happen behind the scenes other than a User switching it

skrawczyk · Answer

like a default value on an API call or something

Jake Kaplan · Answer

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

skrawczyk · Answer

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

Jamie Zieziula · Answer

thanks jake for the help