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

The message from _2.8_ release does a great job in explaining the work pool and work queue concepts. I feel adding the same information to this <https://docs.prefect.io/concepts/work-pools/|concept doc> will make the doc better

From the docs, it is still unclear to me yet
• whether work queues can be created without being associated to work pools. This <https://github.com/PrefectHQ/prefect/blob/d9dcac6418e14ff58c01ee9c49bbd16a178852ed/src/prefect/agent.py#L95|line in code> implies work pool is optional. Is my understanding correct? 
• do work queue names have to be unique across all work pools. This <https://github.com/PrefectHQ/prefect/blob/d9dcac6418e14ff58c01ee9c49bbd16a178852ed/src/prefect/client/orchestration.py#L969|line in code> implies the work queue names have to be unique across work pools. Is my understanding correct?


Thanks for the feedback! cc <@U03SXGWL1K4> / <@U02GE39K551>

Great questions <@U04UTN3G82F>!
• If you create a work queue without specifying a work pool, then the work queue will be created in the work pool named ‘default-agent-pool.’ We do this to preserve backward compatibility.
• Work queue names only need to be unique within a work pool. The code you linked will retrieve work queues across all work pools starting with the specified prefix.
Let me know if you have any other questions!