@Marvin why does my agent pick up work from a worker type work pool? I noticed that both work pools have a queue named

default

. Could that be it? Also, the names of these work pools are

default-worker-pool-dev

and

default-agent-pool

.

It appears that the shared name for the queues (

default

) in both your work pools is indeed contributing to the issue where your agent is picking up work meant for a different worker type. From the Prefect documentation: - Each work pool can have multiple work queues, and Prefect automatically creates a

default

queue if none is specified. - Each work pool's work queue can be customized to control how work is distributed. However, having a queue named

default

in both work pools can lead to unintended overlap. Workers (similar to agents but with more control and capabilities) operate by polling work from the work pool's queues they are assigned to. If multiple work pools have queues with the same name, it could result in agents or workers misinterpreting where to pick up work from, leading to the behavior you're observing. ### Next Steps 1. Rename Work Queues: Ensure that each work queue has a unique name across your work pools. 2. Check Configurations: Verify the setup of your work pools and queues to ensure they align with the intended execution environments and avoid overlaps. For more advanced control over work delivery, consider creating additional, uniquely named queues within each work pool with specific priorities and concurrency limits. For troubleshooting purposes and to prevent similar issues, refer to the documentation above and pertinent GitHub issues: - Ensure critical flows run even during disconnections - Handling borrowed tokens and retries across agents If these changes do not resolve your issue, investigating these GitHub issues and contributing a detailed bug report or feature request could help uncover underlying problems or inspire new solutions. Should you need more detailed configuration examples or face further issues, let me know, and we can delve deeper.

> However, having a queue named

default

in both work pools can lead to unintended overlap