That's exactly what we came up with here after lots of discussions!  But the problem with this method is that we can submit a new instance of the job but can't rerun the *same* instance.  This will cause versioning issues and require manual intervention in the end, which is what we're trying to avoid.

How about the 'rerun each time dependencies are met' check box in the dependency tab?  Maybe you can use a variable dependency.  Like a job event after the job runs thats sets a variable = 1 if job failed and 0 if success.  Then use that variable as a dependency.

Or maybe you can even use the same job as a job dependency - like if that job completes abnormally.  Again never tried it - it may give you a warning or not allow you to alltogether.

How would I be able to run ANY job that might have "Deadlock" in the <Job Output>

If it was just for 1 job I would store the output of each job into a variable and then create an event/action sequence that reruns the job based on the output but is there an easy way to do this for all Tidal jobs?

We have over 1000 jobs...

  Its probably best to just use Associated jobs tab. That makes it quicker to add many jobs to an event.

Below is the example of relevant selections. OR my recommendation is to add the jobs individually to the associated tab.

I knew there were other ways!