The following items are notable issues fixed between the release of TestStand 2025 Q3 and TestStand 2026 Q1, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of TestStand.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 3697936 |
Higher pre load times experienced when loading TestStand sequencesPreload time is slower than expected for large TestStand sequences that repeatedly call the same VI when that VI resides within a class hierarchy inside a PPL (Packed Project Library). Although caching should occur after the initial load, subsequent loads still show longer‑than‑expected delays.
Workaround: SequenceFileLoad callback and configure it to call LabVIEWModule.LoadVIInfo for the module VI that is invoked multiple times.Please note that you must call LabVIEWModule.LoadVIInfo for all VIs that are loaded repeatedly within your sequence file.Reference to Help Doc -
|
Reported Version: TestStand: 2023 Q4 | TestStand: 2024 Q4 | TestStand: 2025 Q2 | TestStand: 2025 Q3 | TestStand: 2026 Q1 Resolved Version: N/A Added: Feb 5, 2026 |
|
| 3770347 |
Operator Access Not Restricted in Run-Time Error DialogFor users with the Operator role, all options except Run Cleanup should be disabled. This issue bypasses expected role-based access control and can allow unintended execution during runtime Workaround: Override the callback to display a custom runtime error dialog that includes only the required options. |
Reported Version: TestStand: 2021 SP1 | TestStand: 2022 Q4 | TestStand: 2023 Q4 | TestStand: 2024 Q4 | TestStand: 2025 Q2 | TestStand: 2025 Q3 | TestStand: 2026 Q1 Resolved Version: TestStand: 2026 Q3 Added: N/A |
Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.
These patches currently do not have any special instructions.