Any advice on how to troubleshoot a job being scheduled but not submitted to Kubernetes? I have Prefect Core 0.15.11 with the agent installed in k8s. I ran a first flow which is running still, and then triggered a separate flow that got scheduled in the prefect UI but not submitted to K8S. I don’t say any logs from the agent saying it is deploying the flow run with that ID.

Scheduled but not submitted is more often a labelling issue. What are the labels for Flow and agent?

k8s

and

qa

on both the flows and the agent. Now that the first flow finished the second one got submitted and is now running.

You never set any before? Or you mean none on this specific Flow?

I’ve experimented with task concurrency limits before; however, I am not using them anymore. I double checked the task concurrency page to see if any tasks were used and they weren’t to verify I didn’t add a tag somewhere

Could you try hitting the GraphQL API?

query {
  flow_concurrency_limit {
    id
    name
    limit
  }
}

If this doesn’t return anything, I’m not sure the one flow running after the other is because of concurrency. I think it might have been a coincidence? Unless it repeats?

Ah, I know what happened. After it didn’t run I checked flow concurrency limits and didn’t see any; however, I think I was affected by this bug: https://github.com/PrefectHQ/ui/issues/1190 Your query did return flow concurrency limits and I eventually got that grid to load. So sorry, I did have a flow concurrency limit. Thanks for pointing me in the right direction.

Yeah that makes sense!