Start Copy/Move job in Queue

[Millzey]

I have the queue enabled. I start a copy job and it begins.
I queue up two more jobs and they are pending.
I decide to start the 2nd pending job, and it begins, but when it finishes, the 3rd one begins.

Why does this happen? I didnt want the 3rd job to start.

Thanks

[RalphM]

Just an assumption here, the queue is ticked off in order and you decided to start #2 before #1 was done, so who is to decide whether after #2 is done it should go back to finish #1 first or keep going with #3 as the next job in the queue?

[Millzey]

Dont understand what you mean, but if I right click a job in the queue, it has a Start Now option. That seems to me it would only apply to starting the job I have selected and thats it.

If i start any job while #1 is in progress, every job after that one I start is also started.

[RalphM]

The idea of queuing jobs is to be able to collect them all in the queue and then have them processed one after the other without supervision.
Without any manual intervention on your behalf the queue is processed one job after the other in the order they appear in the list.
By manually prioritizing #2 (by clicking Start Now) you only change the order in which they are processed.

I hope this made it clearer, otherwise someone else might need to give it a try.

[jupe]

I think what he means is that when he manually starts job #2 he wants just that job to run instantly, but from memory what happens instead is that it starts simultaneously running the queue in 2 threads, so when job #1 finishes if #2 is still running it starts job #3 and if when job #2 finishes it starts job #4 and so on, I think from memory I have observed this behavior in the past as well when copying a big queue to my slow NAS, and also thought it was unexpected behavior, what I did to mitigate it was just pause one of the copying dialogs until the queue was finished and then un-paused it.