Retry on failure for Initialization error
Add the option to retry on failure for initialization error. (like a checkbox to allow the retry for the init. error)
In some cases, it can be useful to allow the retry for init error like in the case SMA-00097269 where they ran into a 31010 error as a domain controller was temporary unavailable and a simple restart would have started the job correctly.
Same for the case SMA-00096903 where the AD was locked and automatically unlocked after 15 minutes.
Comments: 5
-
01 Mar, '21
Brady SikesAlso on case SMA-00054503.
We experience both of these situations. As a work around, many of our jobs that run around the time our DC servers reboot have events to restart themselves if the end code is 31010. Would love it if those weren't needed though. -
24 Aug, '21
Brady SikesWe've been getting a couple 31007 errors the past couple of days, and these too don't respect the retry on failure frequency setting. The job runs normally when manually restarted, so it would be really helpful if ALL failures followed the frequency settings, or if there was a checkbox as the idea suggests to override the default functionality.
-
24 Jan, '22
BradyReceived another 31007 error where the job failed to start on the LSAM. Job ran fine when manually restarted, so I suspect it would have been fine if it had respected the job retry logic already setup on it.
-
30 Sep, '22
BradyReceived another 31007 error a couple of weeks ago. So far we've been unable to determine what caused the error, but the job ran fine after we manually restarted it. I would love to know the reasoning for why the "retry on failure" logic doesn't apply to these kind's of failures. These errors have the potential to bring our automation to a halt and need manual intervention to be fixed, which makes no sense with such a robust piece of automation software.
-
10 Oct, '22
JohnThis feature would help a great deal when receiving initialization errors. Placing event restarts are ideal for one job failing but when they are random the logic is not ideal to place them in each job. Having an option to retry with an initialization option would allow the user restart the job if they receive this error.