Job Retry Not working

I tried this myself and it seems to work. The retried jobs show up as nested jobs of the original one.




My script just does this.

throw "Bad"

No kidding! Did you do anything other than just set the retry limit value? lol my script failed 2 days ago and i dont have anything for retries…

I suppose my test isn’t truly a one liner, but am i just over coding it with the try catch or something?




My trigger scripts for other failed jobs seem to be working just fine, but the Lou.ps1 job just never had any retries or nested jobs.




*Edit – updated pic and notes to show no nested jobs

We are dealing with the same thing, we can’t get retries to work.

A foreign_key error (SQL Server backend) is thrown when a job fails and anything but 0 is specified for retry limit.

Quick updates and a couple followup questions –

Updating to 4.1.4 got the retries working. One odd thing i noticed is that only my first retry (set to 3 retries) is nesting in the original “parent” failed job. Each retry seems to be nesting in it’s own, new job.

(original failed job)



Looking at all of the jobs, it looks like all of the retries are triggering from a manual run, however the only job that i manually ran was 2329 – the original job that trigged all 3 retries



My use case here is an employee separation processes. I have one parent script that invokes about 7 sub scripts (that process different sep processes on different applicaitons). The parent script waits for all 7 sub scripts to finish, pulls any pipeline output , throws it all into json and logs it. In the event that one of the sub script fails, I do want that sub script to retry (for as many retries as specified), but if those retries dont all nest under the originally failed job, I wont be able to track all of the retried jobs to find any available pipeline output

thoughts?