Of course NOT. There are two main parameters we need to give profound focus, which are nothing but detecting Job Warning in the Job and, if warnings, aborting the Job Sequence with restartablility.Of course. However, like most of the time, there's more than one way to skin this cat. All I was attempting to point out was that (in my opinion) the focus on just warnings was too narrow, but that rather you should handle all outcomes outside of the 'OK' box.
What I got when I experimented with your new solution:1. It's all there, not sure what makes you think anything is missing. Why not build what I suggested and verify for yourself that it does indeed restart when appropriate.
2. Of course, by definition it covers all situations not otherwise covered by the existent triggers. Your 'abort with no warnings' scenario is... odd. The goal here is a Sequence which is restartable when there is any kind of problem. As Ray noted, there is no need for any other solutions as solutions have been given. You just parroted what Ray said and drew some lovely ascii art. After retracting the first "that isn't true" misstep on my part, I posted an alternative. Both satisfy the requirement.
When the selected Job1 gives OK status and Job2 produces warning(s) at any point of time, flow validates Trigger [Otherwise] and makes Job Sequence aborted in restartable condition with the help of Sequencer Activity and Terminator Activity at the end. Here the notable point is that Job2 is not aborted and so the checkpoint is not recorded at this point. Later then, when I restart my Job Sequence, the execution of Job1 and Job2 is skipped(checkpoint not recorded here) and the Job Sequence is always aborted in restartable condition with the help of Sequencer Activity and Terminator Activity.
Your 'abort with no warnings' scenario is... odd. The goal here is a Sequence which is restartable when there is any kind of problem.
For your information:pat_raman2000 wrote: My requirement is when it encounters warning it should abort and be there at Job1
In the Job Sequence, the checkpoints are NOT added when an unhandled abort encountered in Job.
In other words,
1. When the Job is aborted and the abort condition is NOT handled in the Trigger section, the checkpoint is NOT added.
2. When the Job is aborted and the abort condition is handled in the Trigger section, the check point is added.