Setting Sequence Pass/Fail Status Based on Repeated Step Results

Updated May 1, 2026

Issue Details

In TestStand, even though the same Step can be executed and Pass or Fail multiple times (e.g. when using the Goto Flow Control step to execute the same Step again), if the Step fails at least once, its Sequence Status will be set as Failed.

 

Is this intended? How can I control the Sequence Status based on a repeating Step's result?

Solution

This behavior is expected. Note that, with default settings, any failed Step will cause the Sequence to fail.

You can change this behavior using any combination of the following options below:

 

  • This behavior can be directly changed with a checkbox for each Step individually. Enable/disable the Step Settings pane >> Run Options panel >> Step Failure Causes Sequence Failure option.

    • When you enable the Step Failure Causes Sequence Failure option, TestStand sets the sequence status to "Failed" when that step fails. (RunState.SequenceFailed = 1)

  • You can use the Looping Step Property to iterate over the same Step multiple times. Even if some iterations have failed during the loop, the final result of the Step (Step.Result.Status) is defined by the loop configuration after the loop ends.
  • You can programmatically access/modify a given Step's Status (Step.Result.Status) or a Sequence's Status (RunState.SequenceFailed). This lets you configure each status separately.
    • Step.Result.Status - the Status property is not Boolean, it has a String type. Use "Passed" or "Failed". For other Status strings, see: Step Status - TestStand User Manual.
    • RunState.SequenceFailed - this property is a Boolean.
    • This is independent from the Step Failure Causes Sequence Failure option. Programmatically changing the Step.Result.Status will not automatically change the value of RunState.SequenceFailed.