Tetra Biacore Insight Connector v2.x Release Notes

Release notes for Tetra Biacore Insight Connector versions 2.x.

The following are the Tetra Biacore Insight Connector release notes for versions 2.x. The Connector is a standalone, containerized application that receives evaluation data from Cytiva Biacore Insight and then uploads it to the Tetra Data Platform (TDP).

v2.0.1

Release date: 16 October 2026

TetraScience has released a patch for the Tetra Biacore Insight Connector, version 2.0.1. This release keeps the Connector uploading evaluations after its Biacore Insight authentication token expires, and prevents a failed polling cycle from skipping evaluations.

Here are the details for what's new in Tetra Biacore Insight Connector v2.0.1.

New Functionality

There is no new functionality in this release.

Enhancements

There are no enhancements in this release.

Bug Fixes

The following bugs are now fixed:

The Connector no longer stops uploading evaluations about one hour after it starts. Previously, when the Biacore Insight authentication token expired, token refresh requests failed with a Token was not valid error, and uploads stopped until the Connector was restarted. The Connector now refreshes the token before it expires, and signs in again if Biacore Insight rejects a request as unauthorized.
The Connector no longer skips evaluations that were modified while a polling cycle failed or only partly completed. The next successful polling cycle now picks up every evaluation modified since the last successful cycle. After a failed cycle, the Connector reports a Critical health status until a cycle succeeds. After an extended outage, that first successful cycle can take much longer than a normal one.

Limitations

The largest evaluation validated end to end against a Biacore Insight server in a TetraScience test environment was about 8.4 GB. Larger evaluations weren't tested. It's recommended that customers include representative large evaluations in their validation.
Download time depends on the rate at which the Biacore Insight server sends evaluation data. Large evaluations can take hours to upload.
For large evaluations, the Biacore Insight server can take more than a minute to start sending data. If large evaluations fail with timeout errors, increase the HTTP Read Timeout (seconds) parameter. For more information, see HTTP Read Timeout (seconds) in the Tetra Biacore Insight Connector User Guide (v2.0.x).
After you restart the Connector or save its configuration, the Connector reports a Healthy status as soon as it signs in to Biacore Insight, even if a catch-up polling cycle is still running.

Deprecated Features

There are no deprecated features in this release.

For more information about TDP deprecations, see Tetra Product Deprecation Notices.

Known and Possible Issues

There are no known issues for Tetra Biacore Insight Connector v2.0.1.

Upgrade Considerations

Customers can upgrade directly to Tetra Biacore Insight Connector v2.0.1 from v2.0.0 with no configuration changes. Customers upgrading from v1.0.0 should also review the upgrade considerations for v2.0.0.

You can deploy the Connector in the cloud or on-premises to either a Tetra Hub or as a containerized Standalone deployment.

🚧
IMPORTANT
If you're upgrading from v1.0.0, v2.0.x replaces a wider set of characters in uploaded file names, and a / in an evaluation name no longer creates a folder in the uploaded file's path. If pipelines, searches, or other downstream processes match on exact file names or file paths from v1.0.0, verify that they still match after upgrading.

For more information, see the Tetra Biacore Insight Connector User Guide (v2.0.x).

v2.0.0

Release date: 2 October 2026 (updated 16 October 2026)

TetraScience has released its next version of the Tetra Biacore Insight Connector, version 2.0.0. This release adds support for organization TLS certificates and a configurable HTTP read timeout. It also expands file name sanitization, removes the generated report point table from uploaded evaluation files, and streams evaluation downloads.

Here are the details for what's new in Tetra Biacore Insight Connector v2.0.0.

New Functionality

New functionality includes features not previously available in the Tetra Biacore Insight Connector.

Organization TLS certificate support: The Connector can now connect to Biacore Insight servers over HTTPS by using self-signed or private SSL/TLS certificates uploaded to the TDP on the Organization Settings page. Certificate validation stays enabled. For more information, see Use Organization TLS Certificates in the Tetra Biacore Insight Connector User Guide (v2.0.x).
Configurable HTTP read timeout: The new optional HTTP Read Timeout (seconds) parameter (httpReadTimeoutSeconds, default 120 seconds) sets the longest time the Connector waits for Biacore Insight to respond or send more data when downloading an evaluation. It doesn't limit the total download time. For more information, see HTTP Read Timeout (seconds) in the Tetra Biacore Insight Connector User Guide (v2.0.x).

Enhancements

Enhancements are modifications to existing functionality that improve performance or usability, but don't alter the function or intended use of the system.

Streaming evaluation downloads: The Connector now downloads and processes evaluation data from Biacore Insight in chunks as it arrives.
Expanded file name sanitization: The Connector now replaces the following characters in evaluation names with an underscore (_) in uploaded file names: / \ < > : " | ? *. When a file name is changed, the Connector adds original_filename and sanitized_filename labels to the uploaded file. For more information, see File Names in the Tetra Biacore Insight Connector User Guide (v2.0.x).
Report point table removed: The Connector no longer adds a generated report point table to uploaded evaluation files. Uploaded files contain the evaluation data as exported by Biacore Insight.
New Manual Upload command name: The Manual Upload command action is now TetraScience.Connector.BiacoreInsight.ManualUpload.v1. The previous action name, TetraScience.Connector.BiacoreInsights.ManualUpload.v1, is still supported.
Recovery of interrupted uploads: When the Connector starts, it sets any files left in PROCESSING status to ERROR, and then retries them on the next polling cycle.
Product name correction: "Biacore Insights" is corrected to "Biacore Insight" throughout the Connector.

Bug fixes

A / in an evaluation name no longer creates a folder in the uploaded file's path.

Limitations

The largest evaluation validated end to end against a Biacore Insight server in a TetraScience test environment was about 8.4 GB. Larger evaluations weren't tested. It's recommended that customers include representative large evaluations in their validation.
Download time depends on the rate at which the Biacore Insight server sends evaluation data. Large evaluations can take hours to upload.
For large evaluations, the Biacore Insight server can take more than a minute to start sending data. If large evaluations fail with timeout errors, increase the HTTP Read Timeout (seconds) parameter. For more information, see HTTP Read Timeout (seconds) in the Tetra Biacore Insight Connector User Guide (v2.0.x).

Deprecated Features

There are no deprecated features in this release.

For more information about TDP deprecations, see Tetra Product Deprecation Notices.

Known and Possible Issues

The following are known issues for Tetra Biacore Insight Connector v2.0.0:

The Connector stops uploading evaluations about one hour after it starts, when the Biacore Insight authentication token expires. Token refresh requests are rejected with a Token was not valid error. Restarting the Connector restores uploads until the token expires again, about one hour later. To resolve the issue, upgrade to v2.0.1. Status: Known since v1.0.0. Fixed in v2.0.1.

Upgrade Considerations

Customers can upgrade directly to Tetra Biacore Insight Connector v2.0.0 from v1.0.0.

You can deploy the Connector in the cloud or on-premises to either a Tetra Hub or as a containerized Standalone deployment.

🚧
IMPORTANT
v2.0.0 replaces a wider set of characters in uploaded file names than v1.0.0, and a / in an evaluation name no longer creates a folder in the uploaded file's path. If pipelines, searches, or other downstream processes match on exact file names or file paths from v1.0.0, verify that they still match after upgrading.

📘
NOTE
On the first start after upgrading, the Connector sets any files left in PROCESSING status to ERROR, and then retries them on the next polling cycle. These files can appear with ERROR status on the Connector Details page until the retry completes.

For more information, see the Tetra Biacore Insight Connector User Guide (v2.0.x).

Other Release Notes

To view other Tetra Connector release notes, see Tetra Connector Release Notes.

Updated 7 days ago

Did this page help you?