Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Hey all, I still am confused about the `work queue` and `work pool` behavior :thinking_face:

I have created a deployment with work queue `wq1`.
I have created a prefect agent with work queue `wq1`.
• `Agent started! Looking for work from queue(s): wq1...`
When I trigger a flow via API, it is shown as:
• work pool: `default-agent-pool`
• work queue: `wq1`
However, the agent does not pick up that flow run :thinking_face:

Any thoughts or suggestions?

PS: I did it similarly before and it worked before, I think.
PPS: I redeployed the flow already several times (i.e. whenever I needed to restart the related EC2 instance).

PS: the `wq1` workpool currently shows as `Unhealthy` even though the prefect agent is running :thinking_face:

OK, I found the problem :blush:

One flow run was still in `PENDING` state.

I guess because a previous prefect agent did not shut down properly? :thinking_face:

cancelling the PENDING flow run allowed the prefect agent to pick up a new run, I guess because of my flow run concurrency settings