"Run Now" available while a backup is running

[JonMikelV]

@mikaitech

Someone can click Run Now 5 times, and it will queue the same backup 5 times in a row.

It’s not supposed to work that way so if that’s what happens for you, please let us know.

Duplicati should not be adding a job ID to the queue (as in waiting to run, NOT what’s currently running or scheduled to run in the future) if that ID already exists in the queue.

So you should be able to cause one back-to-back run of a job (currently running + queue to run next) but more than that shouldn’t be possible unless you wait until the “queue to run next” job moves to running then manually queue another one.

@sylerner

For that matter, is the queue currently visible?

Yes, but it’s very ugly. If you go to the main menu “About” page and select “System Info” then scroll down to the “Server state properties” section there are a set of fields called “proposedSchedule” and “schedulerQueueIds”.

See this post for an explanation of how to read the field contents (but like I said, it’s ugly):

Backup is not "finished" even though Last successful run shows start and elapsed time

If you go to the main menu “About” -> “System info” and scroll down to “Server state properties” you should see many fields including: “activeTask” (What’s currently running) “proposedSchedule” (what should happen eventually but isn’t currently in the queue like manually added jobs or the NEXT scheduled run of a job that might currently be running) “schedulerQueueIds” (what’s currently in the queue to be run) If a job runs long enough that it goes past it’s next scheduled run time, it will be…

@sylerner

A possible future feature should be the ability to display the queue and move jobs up and down the list as well as delete jobs.

Yes, this is something that has been requested before, unfortunately the way the queue has been written makes that extremely difficult. However, I believe there is a queue rewrite in the works which, when done, should make features like that much more viable.