When a scheduler can't acquire the advisory lock, it returns from its run method. But this also causes jobs to exit from their run methods which isn't really what we want. Instead the job should continue and ignore the fact that a scheduler can't be run (another is probably already running anyway).
When a scheduler can't acquire the advisory lock, it returns from its run method. But this also causes jobs to exit from their run methods which isn't really what we want. Instead the job should continue and ignore the fact that a scheduler can't be run (another is probably already running anyway).