Job chain step maximum restart <#> on error triggering additional step with skipped status

[Former Member]

Hi All,

We have business requirement to restart the job step automatically if it errors 1's, So we have configured the Job chain with Final Status Handlers on Error "Restart Step" Action and also set the maximum restart to 2 (includes initial run). 

Auto restart on error of step is working fine, but its triggering total 3 runs of that same step with 1. Error, 2. Error and 3. Skipped status.

Ex.  Job chain Z_Test_Chain has 3 steps and if step 2 error's then we need this same step to be auto restarted only 1 time.

              Z_Test_Chain

                     Step 1-->Step 2-->Step3    

Out put status after run.

          Z_Test_Chain --    Error

          Step 1            ---   Completed

          Step 2            ---   Error

          Step 2            ---   Error

          Step 2            ---   Skipped

          Step 3            ---   Chained

Step 2 is getting restarted as we expected but every time we see additional step 2 with skipped status along with the auto restart.

let me know if any one experienced similar issue and why CPS triggering that additional step which is not required. Let me know if you need additional details on this issue.

Thanks

Nidhish.

[gmblom]

Hello,

This is as expected. The Skipped step can help you decide what you want to do next using the Otherwise final status handler.

Regards Gerben

[Former Member]

Hi Blom,

Thanks for your response.

I agree with you about the Skipped step might help us to decide the next action, but in our case we are once we get this step2  failed twice the Parent job chain to be Error out and send alert without proceeding to next steps.  So is there any alternate way that can we avoid of getting this additional skipped step 2 entry from the job chain? which will help the users to not to be confused when they expand the chain in monitor screen?

Thanks,

Nidhish

[former_member237959]

As Gerben said, if you want to proceed to step 3, you use the Otherwise final status handler in your case. If you want to avoid the additional entry, you can put the restart condition at the job chain or job definition level.

Thanks,

Lohit