A database restoration has been performed on March 11 (Tuesday), 2025. The database was restored to its state as of February 26 (Wednesday), 2025.
It has been observed that a background job, which is scheduled to run on Mondays, was executed on Wednesday, March 12. (But posted on March 11 (Tuesday))
Given that the background job is scheduled to run on Mondays, it did not execute as per its schedule. In such cases, does the job automatically execute as soon as the database is restored and operational?
Best answer by sdhalk
Based on the investigation, the following is the answer:
After a database rollback, if the next scheduled execution date of a background job falls in the past (relative to the restored database state), the job automatically executes as soon as the database is restored and operational.
In this case, multiple background jobs were posted around the same time, and some took longer to execute. As a result, the jobs were processed sequentially, leading to the observed delay between the "Posted" state and the actual execution on March 12, 2025.
Based on the investigation, the following is the answer:
After a database rollback, if the next scheduled execution date of a background job falls in the past (relative to the restored database state), the job automatically executes as soon as the database is restored and operational.
In this case, multiple background jobs were posted around the same time, and some took longer to execute. As a result, the jobs were processed sequentially, leading to the observed delay between the "Posted" state and the actual execution on March 12, 2025.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
