Hi @UR-Stelle
I only see 2 pending jobs in the queue right now, though it’s also giving me the 792 minute estimate.
We did have an issue with low disk space in Flukebook and Zebra Codex that fixed yesterday. That estimated time is based on how long it took to process more recent jobs and since the server was low on disk space, that estimate is not likely to be accurate.
To reference a previous post from Jason on the matter:
One thing to keep in mind with the time estimate: it is a reflection of past work only and doesn’t make a prediction. The last job may have taken 18 minutes to turnaround, but if the queue is empty, it may not take 18 minutes for a new job. Currently, the time estimate is noting that the turaround time is about 15 minutes, but in fact there is nothing in the queue, so a single ID job is likely to complete much, much faster than that.