Replies: 2 comments
|
Hi! Yes, this is already how xyOps handles retries and job actions. Configure the job with your desired Retry limit, then add an Email action with the condition set to On Any Error. When a job attempt fails and xyOps launches a retry, completion actions are not executed for that failed attempt. Therefore, you will not receive an email for every retry. The error action will only run if the final attempt fails and there are no retries remaining. If one of the retries succeeds, the error action will not run. Any configured success or completion actions will run once for that final successful attempt. One small clarification: 10 retries means up to 11 total attempts, consisting of the original attempt plus 10 retries. This behavior applies when the scheduled job is launched and subsequently fails. It does not detect a schedule that was missed entirely because the scheduler was offline. Relevant documentation: |
|
Honestly, that's so much better than I'd hoped for. thank you! |
Uh oh!
There was an error while loading. Please reload this page.
Is there a way to delay sending an event until after any retries have been attempted?
Example, we have a job, it must run at 4am. If it doesn't, it'll send an alarm. If i enable retries, it'll alarm until it succeeds right? (I have 10 retries, so that'd be 10 emails).
I'd like it to try until it either a) succeeds, or b) runs out of retries, then sending the panic alarm to wake me up.
Is this possible currently?
All reactions