👋 typingcat hey all! I'm setting up a new deployment, and it looks like all of my deployments are getting stuck in a Late state. seems like the runs from the previous days got stuck there too. I canceled them, and tried deleting my deployment, rescheduling it, but same result. I also tried deleting the new deployment, creating a new workpool, (as suggested by another slack member experiencing this issue) and then re-running it, and same result. Can anyone assist here? thank you!!!

hi @lauren.benezra! I suspect there is some issue with your worker (if you're not using a push work pool type): • what kind of work pool do you have? • (if applicable) where is your worker running? does it have logs?

thank you for your quick response, Nate! Also I'm new to prefect, so apologies if I ask silly questions or provide silly answers. It is a Push workpool, manged by prefect.

no worries at all 😄 you shouldn't need to worry about a worker here! if you have access to the prefect CLI, can you run

prefect work-pool ls

and share the output for this work pool?

yes!

hmm so since its managed and you don't have a concurrency limit, the main two gotchas should not be applicable let me poke around and see if I can see something weird going on. would you be willing to DM me a URL from the UI? the url contains your account and workspace ID

absolutely! doing so now. ty ty ty

I think this is a known bug Lauren. I had the same thing and ultimately couldn't use prefect managed workers for this reason unfortunately

thanks for the input @Matthew Bell! we resolved this in a DM - in this case the shared concurrency slots were full. we will do more to surface when that is the case

Ah I see, thanks for sharing