Scheduled job delays while environment down

taylor

We had to unexpectedly take our Decisions environment temporarily while we fixed a security issue. When we started the environment back up we noticed that a bunch of scheduled jobs that were supposed to run overnight instead ran during the day right after the environment started. Why did that happen and how can we avoid this in the future?

Note that we have Requeue Failed Action enabled for all of these scheduled jobs.

Kathryn_Decisions

The Reque Failed Action setting is the reason why this happened. Depending on how long your environment was offline, when the environment comes back online, the environment realizes that certain jobs should have run during the time period while it was down. It will then queue those jobs it would have run.

You can this in the future by disabling the Can Be Job Server setting temporarily before the environment goes offline. This setting is located by going to System -> Administration -> Servers, selecting the machine, and unchecking Can Be Job Server. However, please make sure after the environment comes back online, you re-enable that setting or scheduled jobs will not run on that machine.