Queue file operations breaks if one job started manually

[o7blue]

Basically if I queue up a bunch of jobs and start the most recent one manually, it will cause both the manually started job and the next queued job to start. This can stack as well- each manually triggered job triggers another queued job, regardless if it's time for it or not.

video example: https://youtu.be/Gc0VFe5oky0

[admin]

The video seems rather blurry. Describe in words what is happening and what you expect to happen instead.

[o7blue]

Might have been the recency, but the video is processed up to 4K now, shouldn't be blurry anymore.

But in words:
-I queue up 4 jobs
-Job 1 is in progress jobs 2-4 are pending
-I manually start job 4
-Job 4 starts, once job 4 finished job 2 starts while job 1 is still in progress

From what I remember how job queuing worked a few versions back, job 2 should start only when job 1 finished.

[admin]

Thanks. I'll look into it.

[admin]

Should be fixed in next beta.

[o7blue]

Pending jobs are no longer triggered by manually started jobs on my end on the latest beta release, thank you!