View reason for job being queued

When a job is queued the text “Starting your workflow run…” is displayed, but that seems to be it. I am not able to figure out why it is not already started.

I would like to see which labels it is waiting for and which number in the queue it is. I don’t know if it could be other reasons than label contention that can cause a job to wait, but if it is another reason, that should also be possible to see.

This would be really helpful in debugging bottlenecks in the workflows and to decide which labels we should invest in getting more of to speed up a workflow. For example; buying more GPUs of a particular vendor, more CPUs, more signing keys, more licenses for the embedded C compiler and so).

Is it possible to get this info out today? Is it on any roadmap?

We’re currently working on improving experience especially when a job is in a queued state. In a couple of weeks, you should be able to see more info apart from “Starting workflow run…”.

1 Like