Good afternoon! I'm looking into prefect as a replacement for a homegrown data pipeline solution. I'd like to learn more about the different ways of prioritizing flows (work). My usecase- our products will often run on edge deployments with hardware constraints. Suppose I prioritize my different data products, and work backwards and identify the flows and pipelines that create them. Everything tagged critical would always run first. And everything below that (high, medium, low) would have a weighted priority based queue and run whenever it is able to. Is there a way to accomplish this in prefect without artificially throttling the lower priority work when no higher priority work is present? • I saw a thread from 2 years back where a person suggested managing priority by setting different concurrency levels for the different queues. This would presumably cause the low priority work to back up even when no higher priority work was present.

hey @Patrick Stevens! welcome have you checked out work queue priority at all yet?