Skip to main content

Queue visibility in the UI

Feature Requests

The current Pending runs count is misleading because it lumps together high-priority and low-priority (e.g. drift detection) runs without any distinction. Users can see a large pending number vs. a small worker count and panic.

  • Surface run priority/ordering in the queue UI

  • Show expected wait time or at least a priority-aware count something like: Workers: 6  Busy: 6  Pending: 7 (+ 183 low-priority tasks) as a quick win, with a long term goal of an AI-estimated wait time in minutes.

2 comments

Log in to comment and vote

Comments2

  • Brown Mole

    •

    Sep 24

    This would be great. I was about to open a similar feature request:

    it would be helpful to have more information on the "run queue" view here. 1207 pending runs seems like a lot, but if I take a closer look, 1201 of those are drift detection runs which should be lowest priority (and we have a lot of these pretty much 24/7). It would be really nice if it could expose how many runs are ahead of this job in it's actual priority queue (it's fine to still show the full size of the queue too)

  • Teal Pigeon

    •

    Jul 16