TestStand Semiconductor Module 2026 Q1 Known Issues

Overview

This document contains the TestStand Semiconductor Module known issues that were discovered before and since the release of TestStand Semiconductor Module 2026 Q1. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.

 

Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community; see Additional Resources.

Bug Number

Legacy ID

Description

Details

3823846, 3851339

Synchronizing Threads In A Multisite Execution Using LabVIEW Reports An Error When Alarms Are Enabled

When synchronizing threads in a Multisite execution using LabVIEW, if an instrument in the test program contains a set of alarms but another instrument in the same session only supports a subset of these alarms, an error occurs.

Workaround:

You may need to assign unique channel group names to each instrument which supports alarms to work around this issue.

Reported Version:

TestStand Semiconductor Module 2024 Q3.1

Resolved Version:

N/A

Added:

N/A

3668454, 3750098

Pin Map Editor Throws A Schema Error If Your Tester Definition File Contains Duplicate Entries

Workaround:

You may be able to work around this issue by removing the duplicate entries from your tester definition file (TesterDefinition.xml).

Reported Version:

TestStand Semiconductor Module 2026 Q1

Resolved Version:

N/A

Added:

N/A

3852078

Test Limits Editor Does Not Navigate Search Results In Order

When a search within the Test Limits Editor returns multiple results, and you then modify the order of the displayed results (for example, by sorting the results by a specific column), functionalities such as 'Find Next' and 'Find Previous' continue to navigate the results according to the originally displayed order.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand Semiconductor Module 2026 Q1

Resolved Version:

N/A

Added:

N/A

3852084

Test Limits Editor Does Not Clear Search Results When No Test Limits Files Are Selected

When you view search results in the Test Limits Editor and you clear all test limits files from the search, the result status still displays the last results from when a test limits file was selected.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand Semiconductor Module 2026 Q1

Resolved Version:

N/A

Added:

N/A

3054716

You Cannot Add Data to an Empty Limits File in the Test Limits Editor

If you open an empty test limits file using the Test Limits Editor, such as a file containing the required header but no other data, and add a new row, the application crashes when you attempt to edit that row.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand Semiconductor Module 2024 Q3 Patch 1

Resolved Version:

N/A

Added:

N/A

3810245

Test Limits Editor Regards an Empty String as Search Text

Typing a partial query in the search box of the Test Limits Editor may immediately run a search before you finish typing the remainder of your query. For example, if you attempt to search "pin=vcc", the Test Limits Editor immediately reports: No matches found for "" in column "Pin" after you have only typed "pin=". Continue typing to complete your query to find the results you are searching for.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand Semiconductor Module 2026 Q1

Resolved Version:

N/A

Added:

N/A

3839683

You Enable Trace Logging While Using the Test Program Performance Measurement Tool and Encounter Errant Behavior

Enabling Trace Logging while using the Test Program Performance Measurement Tool may result in errant behavior. Some examples of this behavior include the application hanging, intermittent errors reported in the log file from the trace logging service, the IOTrace application continuing to run after the measurements are complete, and so on.

Workaround:

We recommend that you do not enable Trace Logging while using the Test Program Performance Measurement Tool.

Reported Version:

TestStand Semiconductor Module 2026 Q1

Resolved Version:

N/A

Added:

N/A

3842626

The Assign Test Numbers Tool Does Not Assign Numbers to Tests on Semiconductor Sequence Call Steps

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand Semiconductor Module 2026 Q1

Resolved Version:

N/A

Added:

N/A

3845661

Long Step Names Appear Truncated in the Test Number Assignment Report

Long step names are truncated in the Test Number Assignment Report that is generated by the Assign Test Numbers Tool.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand Semiconductor Module 2026 Q1

Resolved Version:

N/A

Added:

N/A

3845681

The Test Number Assignment Report Contains Incorrect Conflict Information for Some Steps

When you use the Assign Test Numbers Tool and your test program contains multiple steps having the same name and using the same test numbers, the Test Number Assignment Report incorrectly reports those steps as having: Conflicts Due To Enable Test Number Generation Increment Settings.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand Semiconductor Module 2026 Q1

Resolved Version:

N/A

Added:

N/A

3852086

Search and Replace Keyboard Shortcuts are Functional Even When the Search Panel is Not Open

Search and Replace keyboard shortcuts (such as Replace All) are still functional even when the Search and Replace panel is not open in the Test Limits Editor.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

TestStand Semiconductor Module 2026 Q1

Resolved Version:

N/A

Added:

N/A

Final Time Issue Listed

Issues found in this section will not be listed in future known issues documents for this product.

There are currently no issues to list.

Additional Resources

Explore Support Content and Product Documentation 

 

 

Ask the NI Community

 

 

Request Support from an Engineer

 

A valid service agreement may be required, and support options vary by country

 

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).