We have some long-running VM backup policies in Kasten v9.
These can take many hours before finishing.
As restore jobs is put “on top” (executed when it is its turn), this can mean 12-20 hours later before it is executed.
I see no reason for waiting that long, as a number of subjobs are running meanwhile in VM policies, so the restore could be “inserted” as next thing to do as soon as there is a free slot, instead of waiting at the end of the queue.