In subsequence, a stepfailure aborts the subsequence.

[Mikael_Azelio]

In my MainSequence, I call a subsequence. 

Inside that subsequence there are a lot of tests/logic implemented, but when a step fails, the subseq is aborted directly and send me back to MainSequence. I do not want that behaviour, I would like that the subsequence performs until the end of it...is this possible?

A solution is of course to perform the steps in MainSequence, instead of calling a subsequence...but I´d rather see a solution that where I can use subsequences that not aborts when stepfailure occurs...

[Narayan@GD]

You can try this,

Go to...

Configure->Station Options->Execution (look for On runtime error)..choose show dialog..by default it may be set to abort

[Mikael_Azelio]

It was set correctly...

[Mikael_Azelio]

I might explain better.

MainSeq calls SubSeq.

Inside SubSeq a MultipleNumericTest fails which lead to exit from SubSeq back to MainSeq.

I do not want this to happen, I want to execute all steps in my SubSeq even though a MultipleNumericTest fails...

[Narayan@GD]

Ok.

Click on the step->Step settings pane->post actions->on step failure->select(Go to next step)

[Mikael_Azelio]

Already done...this is what I want to happen.

When step is failing, Goto next step is chosen, but it will not happen, since it throws back to MainSeq instead...

Really strange behaviour. I do not understand why SubSeq is aborted back to MainSeq instead of follow the settings in Post Action....

[Narayan@GD]

Check with this example ......if not check your conditions

[Mikael_Azelio]

That sample was working properly, no issues at all.

I attach my Sequence, which according to me is OK.

The faulty behaviour starts in the calling of subseq 'Internal Supply Tests'

Inside this seq, Check Faultcodes failing, and instead of follow the setup in Post-Action, it will be aborted back to MainSeq...

Is there any global setting in TestStand that could cause this behaviour?

[Mikael_Azelio · Accepted solution]

I re-created the sub-sequence, and the error is gone!

[Matthew.Presley]

Mikael_Azelio, did you ever find the source of the problem?