Scheduled jobs restart following application node restartIssue When viewing scheduled job execution logs you may notice that some appear to trigger more frequently that expected. For example a job scheduled to trigger once per day actually runs twice. If this occurs it is worth reviewing Diagnostic Events to confirm if any application nodes have restarted during the first job execution period When an application node restarts all transactions running will be terminated, these are both user and background events. The user transactions cannot be restarted automatically, and require the user to trigger them again as required. However a scheduled job will remain queued to the restarted node and in a running state which allows it to be re-triggered. This is completed as part of the node restart process to ensure that any required scheduled jobs are not missed. If this was not the case then user may not receive scheduled reports or imports may not be completed until the next scheduled execution. As such this behaviour is expected The only point to note is that if a scheduled job is terminated following a restart it does not remember where it was stopped and will always restart from the beginning again. Because of this the new execution will take just as long as normal but may duplicate actions already completed.