NI TestStand Idea Exchange

About NI TestStand Idea Exchange

Do you have a feature idea for how to improve NI TestStand? Submit and vote on ideas now!

  1. Browse by label or search in the TestStand Idea Exchange to see if your idea has previously been submitted. If your idea exists sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea. Be sure to submit a separate post for each idea. Note: the TestStand Idea Exchange is not the appropriate forum to submit technical support questions.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see implemented!

The TestStand R&D team is committed to reviewing every idea submitted via the TestStand Idea Exchange. However, we cannot guarantee the implementation of any TestStand Idea Exchange submission until further documented.

Showing results for 
Search instead for 
Did you mean: 

Add to the post actions on fail a Fail execution option

Status: Declined

I'm declining this idea due to lack of community support.



As in subject,


It would be good to have the Fail execution option. When the step will fail the execution pointer shal be moved to clean-up part of the sequence (and parent sequences) and the whole execution will be marked as failed



Active Participant

Explain how what you want is different han choosing

On Fail >> Goto Step and choosing step <Cleanup>

Active Participant

When you do On Fail >> Goto Step and choosing step <Cleanup> you finish the cleanup and the parent sequence will be still executing.


The point is to do the CleanUp in the all parent sequencies and finish the sequence with Failed status/ not to terminate the sequence.

Trusted Enthusiast

Is there a reason why the station option to goto cleanup on sequence failure would not work in this use case? Do you need this on a per step basis?

Active Participant

Yes it is. The settings in station option is a global. I see a need of this feature to be applied step-wise rather than sequence-wise.

Proven Zealot

Do i understand correctly that you request a termination of the sequence without having the state of the DUT to be "terminated"?

CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
Active Participant

Yes Norbert, you do.


I request termination with having it marked as failed.

Active Participant
Status changed to: Declined

I'm declining this idea due to lack of community support.

There are critical failures and there are soft failures.
I also need this cascading cleanup to occur on the critical failures.  
Station Options isn't a viable alternative as that affects all executions causing all failures to be treated the same.


To get around this limitation on every critical failure step i need to set

  1. RunState.Sequence.FailureAction to FailureAction_GotoCleanup for the current sequence,
  2. Get my call stack depth
  3. Set the same property for every Caller up the chain.

This feature already exists at the engine level.  Just make it more flexible.