You’re offline. This is a read only version of the page.
Hi all
I was wondering if there was functionality to retry batch jobs that should have run during AOS downtime.
During release an AOS can be down for several hours. Batch jobs that should have been picked up at that moment, will be "missed".
For example: a daily job at 4am will not run that day if the AOS was down at 4am.
Any functionality to make sure it does run?
Or do i really need to code another batch job that checks other batch jobs to run them?! :D
*This post is locked for comments
Guys thanks for the info, i'll try and verify this somewhere this week.
Batch jobs which were waiting will keep their original date stamp when they should run. AX only changes it after the batch has successfully ended in the batch framework and fetch the next slot based on your recurrence settings.
The batch job picks up any waiting tasks, where the start datetime is smaller than the current datetime, that means all your pending batches will execute.
Unless you have customized the batch framework, which has broken the default functionality. You could try this by setting on the batch header to log all execution, and see the Batch job history after your next maintenance.
Hi Tim,
After restart of the AOS, the batch job should run. It is only a bit later. Can you indicate what the status is of the batch job which is not picked up correctly?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,219
Super User 2024 Season 2
#2
Martin Dráb
230,056
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (