In subsequence, a stepfailure aborts the subsequence.

[Mikael_Azelio · Accepted solution]

Hi,

I did not find out what the problem as since after re-creating the subsequence from scratch solved my issue...

/Mikael

[ShockHouse]

I'm just going to add another thing to look at for people who come across this thread.

My guess is you have the Settings, "Step Failure Causes Sequence Failure" turned on.

You can find the setting on every step in Properties -> Run Options. That's what this first picture shows.

Also in Station Options on the Execution pane, you will see a similar thing on the bottom. If your MultiNumericTest had this checked, if it failed it would terminate the execution.

[Matthew.Presley]

I really appreciate the feedback from both of you, especially on a thread that has long since been inactive!

I developed a workaround by placing the steps that I needed to run (with certain preconditions) in the cleanup section in my subsequence. Not optimal, but it got the job done. Then I found the real source of my problem.

My subsequence had the Sequence Property "On Step Failure:" set to "Goto Cleanup" instead of "Station Options". Really simple, but I guess it feels good to have figured it out! 

To find the Sequence Properties of any sequence right click in the Sequence Window, select Sequence Properties, and change it to your preferred setting. Must have been carried over from the previous station options as I am working on some of that good ol legacy software.