@Marvin Can prefect tasks in the same flow run on diffrent work queues?

Let's find out if Prefect tasks within the same flow can run on different work queues by consulting the documentation and relevant GitHub issues. Give me a moment. Based on the information from the documentation and GitHub issues: 1. Documentation Insights: - The Prefect documentation does not explicitly mention assigning different tasks within the same flow to different work queues. Work queues mostly facilitate handling multiple flows and prioritizing flow runs ("priority queues"). - The concept of background tasks and traditional task queue architecture within the same flow isn't deeply discussed in the context of running tasks from the same flow in different queues. 2. GitHub Issues: - The issue on round-robin scheduling of work queues within the same work pool suggests managing multiple work queues. However, this is more about prioritizing and scheduling flow runs rather than tasks within a single flow (`https://github.com/PrefectHQ/prefect/issues/9431`). In conclusion, there is no straightforward feature to assign individual tasks within a single flow run to different work queues. Work queues are designed to manage flow runs rather than individual tasks within those flows. For more intricate task management, you might have to consider architectural patterns or external orchestrations beyond Prefect’s current built-in capabilities. For a deeper dive, refer to: - Work Pools: https://docs.prefect.io/latest/concepts/work-pools/ - Flows: https://docs.prefect.io/latest/concepts/flows/ - Relevant GitHub issue: https://github.com/PrefectHQ/prefect/issues/9431

Can we schedule subflow to run on different work queue?