Error -17300 When Using Wait Step With One Thread Only Sequence in TestStand™ Batch Model

Issue Details

I am running a TestStand sequence using the Batch process model and have a sequence call step with execution options configured to Use New Thread. Synchronization for the called subsequence is also configured as One thread only. When the main sequence reaches a Wait step, I get the following error:

Wait step attempted to wait on a sequence call that has not yet run or that is not a multithreaded sequence call.

ERROR CODE -17300

-17300: Value invalid or out of range.

Solution

In Batch executions, a Wait step can only wait on a subsequence that has already started a multithreaded instance for the current execution. When synchronization for a subsequence is configured as One thread only, this condition is not guaranteed for every socket. To avoid this error, use Batch Synchronization steps instead of thread-based waits to coordinate execution.

Use the following approach:

1. Remove the Wait step that attempts to wait on the One Thread Only subsequence from the main sequence.
2. Move the synchronization logic into the subsequence that performs the shared operation.
3. Use Batch Synchronization steps to control when sockets are allowed to continue execution.
4. Ensure that any convergence timing or result data is finalized before the Exit Batch Synchronization step releases the remaining sockets.

Batch Synchronization steps are socket-aware and do not rely on per-execution thread objects. This makes them the recommended and most robust method for coordinating execution in Batch process models, especially when not all sockets participate in the same operations.