DSXchange

We came across an issue running a scheduled sequence job.
The sequence is scheduled to run on a daily basis.

One day the master (top level) sequence failed due to some reason, then
all the following days the master sequence can not start as scheduled. And
in the log we saw something like this.

Job XXX must be reset before it can run

where XXX is the name of the master sequence.

I didn't find anywhere in the master sequence I can set execution action :
reset if required, then run, as I can do on each induvidual job in the sequence.

Thanks a lot!

Hi,

Your reset button is present in the Director (to the right of the stop button) on the toolbar. If you are not interested in the previous run's logs you can achieve the same status by compiling the sequence.

Regards,

Novak

Novak wrote:Hi,

Your reset button is present in the Director (to the right of the stop button) on the toolbar. If you are not interested in the previous run's logs you can achieve the same status by compiling the sequence.

Regards,

Novak

Can we automatically reset the master sequence?
I know you can click the reset button manually.

Reset can only be had from a controlling sequence. If you build a controlling sequence that does not abort, then it could run your master sequence as "reset if required, then run". That could well be the only job activity (or activity of any kind) in the controlling sequence.

ray.wurlod wrote:Reset can only be had from a controlling sequence. If you build a controlling sequence that does not abort, then it could run your master sequence as "reset if required, then run". That could well b ...

Ray, thanks for the reply.

Is it possible to configure a controlling sequence that will not fail, or will
reset itself automatically after failure? Otherwise my issue still exists, I think.

Of course. Don't automatically handle activities that fail. That alone will prevent the controlling sequence from aborting.

There's no such thing as a Sequence that resets itself. A Best Practice is to schedule a script that that runs your Sequence using dsjob and checks to see if it needs to reset it first. Again, using dsjob -jobinfo and dsjob -run -mode RESET off the top of my head.

I prefer my approach with one sequence to rule them all.

That sequence never aborts so never needs to be reset.