Hello, team! I’m having some issues with my workflows, it seems that they are going into

late

, and staying in there. Any things I can possibly look at? Here is my deployment, it does deploy, but the workflow just does not execute when it should:

deployments:
- name: update-exchange-info-flow-deployment
  entrypoint: exchange_sync_flow.py:update_exchange_info_flow
  work_pool:
    name: main-worker
    job_variables:
      env:
        DATABASE_URL: '*******'
  schedules:
  - cron: '0/1 * * * *'
    timezone: UTC
    day_or: true
    active: true

I am not sure what to check or what to do? Thanks in advance!

what type of work pool are you using?

prefect managed

ah so sorry for leaving you hanging! weekend stuff got in the way

haha no worries

I think this is a known bug, let me see what I can do now that people are around

that would be amazing, thank you so much 🙂

have you had any success running flows at all? it seems like it might be a concurrency limit related thing

interesting, actually, it seems that it’s only related to auto-scheduling, or if i want to run it from the UI. But, if I run my script in my ide, and then the flow gets submitted to cloud, it runs the flow perfectly fine.

ah, that's because the flow run is actually happening locally

ahh yes yes

so every run of a deployment you've ever tried has been stuck in late? Just wanna confirm before making any suggestions

yes yes all stuck in Late

gotcha, I've flagged it internally so we should have some eyes on it soon

ok cool, thank you so much appreciate the effort!!

hey @Jason could you share your workspace id and I can take a look at this?

Hey @Jake Kaplan, Sure! the workspace id is

887a6691-01a1-4ee0-a74e-9046ae5d6050

thank you! will take a look and get back to you here

Ok thank you! @Jake Kaplan

I've identified the issue here. It's related to deleting a deployment that uses a

prefect-managed

pool. A managed pool has a concurrency limit of 1, and that limit can be not cleared (which is a bug). We're in process on a fix. I've manually reset this, so you should hopefully see your runs start to pick up. I'm so sorry for the inconvenience!

Amazing, and no problem @Jake Kaplan , I appreciate the assistance so much. 😁

Hey I think this is a known bug @Bianca Hoch and I were chatting about it a couple weeks back

Yup! Spot on, I think this is related