InstrumentStudio 2025 Q3 Known Issues

Overview

This document contains the InstrumentStudio known issues that were discovered before and since the release of InstrumentStudio 2025 Q3. 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

3174709

System.ValueTuple Run-Time Error When Running Measurement Plug-in Step From TestStand 2025 Q2 and TestStand 2025 Q3

Running a Measurement step in TestStand 2025 Q2 (24.9) or TestStand 2025 Q3 (25.5) may report an error with the Run-Time Error dialog where the description contains a message similar to "Method not found: `System.Threading.Tasks.Task`<System.ValueTuple`..."

This problem can be seen in these versions of TestStand regardless of which version of InstrumentStudio is installed as long as that InstrumentStudio supports that version of TestStand. This issue will be resolved in InstrumentStudio 2025 Q4.

Steps to Reproduce:
  1. Open TestStand 2025 Q2 (24.9) or TestStand 2025 Q3 (25.5)
  2. Drop a Measurement step into the sequence and configure the step to use a Measurement Plug-in
  3. Run the sequence
    Bug: Run-Time Error reports a method no found for `System.ValueTuple`

Workaround:

Unload all modules or restart TestStand.
Then, run the sequence before performing an action that would attempt to configure a Measurement step.

Reported Version:

InstrumentStudio 2025 Q1 | InstrumentStudio 2025 Q2 | InstrumentStudio 2025 Q3 | TestStand 2025 Q2 | TestStand 2025 Q3

Resolved Version:

N/A

Added:

N/A

2756123, 3214362

In TestStand 2025 Q3, using Measurement Plug-in and FlexLogger steps together fail if one is version 2025 Q3 and the other a newer version

In TestStand 2025 Q3 (25.5), using a Measurement Plug-in step and a FlexLogger step will lead to a Run-Time Error if either InstrumentStudio or FlexLogger is version 2025 Q3 (25.5) while the other is a newer version.

It should be okay for InstrumentStudio/FlexLogger mismatches as long as both versions are greater than or equal to version 2025 Q4 (25.8).

The Run-Time Error will include a message saying it could not load GrpcChannelFactory or an exception occurred in MeasurementStepExecution.

Workaround:

Install the same version of InstrumentStudio and FlexLogger. Typically, this should mean upgrading to the newer version.

Reported Version:

FlexLogger 2025 Q3 | FlexLogger 2025 Q4 | InstrumentStudio 2025 Q3 | TestStand 2025 Q3

Resolved Version:

InstrumentStudio 2025 Q4

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).