Hi, I have a question regarding queue priorities. I have a requirement that needs flow runs with "high-priority" to jump all other items in the deployment queue - basically switching from FIFO to LIFO. I saw the documentation on the topic but I don't think I would be able to support such use case. My understanding is that I would need two "low-priority" and "high-priority" queues, but if there is any item in the high-priority, no "low-priority" flow run should start, and I don't think it can be done easily. Are priorities within the same queue something that would be supported in the future, or other ways to work it around? Thanks!

This is an interesting feature request that could be useful for other users. I’ll open an issue for this. @Marvin open “Execute Flows Within a Work Queue Based on Priorities”

I’m curious whether you consider the option to use two queues (one is high-priority and one is low-priority) and start two queues with one agent as shown here

Yes, I had read the docs, but unfortunately that would mean that the agent will pick up jobs as they arrive from both queues. The problem is that these are long running jobs that use shared resources, so only one of them should be running at a given time. I would like to give the user the ability to say: "regardless of the flow runs I have submitted so far, please execute this one as the next one". I don't see how I could achieve that using two queues, but if you have a solution I'll definitely consider it!

Got it. We’ll discuss more about this and keep you updated through GitHub issue