/job/<job_id>/position is misleading #858
Description
This is billed as providing the position in a queue describing at what point the job will be picked up, however there are certainly cases where this is an oversimplification as each agent listens to multiple queues.
Therefore, there could be countless other jobs keeping the agents for the queue which this job is in busy rather than servicing this job.
Originally posted by @ajzobro in #853 (comment)
At any given point, any agent listening to any queue could pop a job on that queue, thereby affecting the number of jobs available to all other agents on that same queue.
Presently, job durations are unknown and at best can be estimated to be the duration of the timeout, even though they may be significantly shorter. Furthermore, each queue may acquire, at any time, a job with a higher priority than current jobs, which would affect the calculation further.