Release date: 11 November 2026

Tetra v4.6.2 fixes issues with file indexing and search, Data Retention Policies, label value suggestions for organizations that use Data Access Rules, Lakehouse schema checks, Health Monitoring, and direct links to Data Apps. It also includes security updates.

📘

NOTE

Tetra v4.6.2 is a cumulative patch release. All new functionality, enhancements, and bug fixes from Tetra v4.6.0 and v4.6.1 are included in this version. For a comprehensive list of capabilities introduced in the v4.6.x release line, see the Tetra v4.6.0 Release Notes.

Key Updates

• Files reliably reach search, Lakehouse tables, and pipelines: Files that hit an error while they're being registered are retried again, instead of being stored without reaching search, the Data Lakehouse, or pipelines.
• Data Retention Policies delete files again: Retention policies that stopped deleting files in Tetra v4.6.0 now run as configured.
• Lakehouse jobs accept newer IDS versions: Lakehouse jobs no longer stop when a newer minor version of an IDS adds fields.
• Direct links to Data Apps work: Users can open a Data App from a bookmarked or shared link without first opening it from its tile.

Here are the details for what's new in Tetra v4.6.2.

Notes

Learn about note blocks and what they mean.

* Any blue NOTE blocks indicate helpful considerations, but don't require customer action.

📘

NOTE

• Any yellow IMPORTANT note blocks indicate required actions that customers must take to either use a new functionality or enhancement, or to avoid potential issues during the upgrade.

🚧

IMPORTANT

GxP Impact Assessment

All new Tetra functionalities go through a GxP impact assessment to determine validation needs for GxP installations.

New Functionality items marked with an asterisk (*) address usability, supportability, or infrastructure issues, and do not affect Intended Use for validation purposes, per this assessment.

Enhancements and Bug Fixes do not generally affect Intended Use for validation purposes.

Items marked as either beta release or limited availability release (previously early adopter program (EAP)) are not validated for GxP by TetraScience. However, customers can use these prerelease features and components in production if they perform their own validation.

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.

Data Integrations Bug Fixes

• The GET /v1/data-acquisition/connectors/{id}/files endpoint no longer returns a 400 error when a filter includes more than 20 values. This affected Tetra v4.6.0 and v4.6.1. A single request still holds about 320 file IDs at most, so larger lists must be split across requests.

Data Harmonization and Engineering Bug Fixes

• Lakehouse jobs no longer fail when a newer minor version of an IDS adds fields. Previously, a schema integrity check that ran before each write treated the new fields as a breaking change and stopped the job. For example, upgrading plate-reader-perkinelmer-envision from v7.0.0 to v7.1.0, or spectrophotometer-thermo-fisher-nanodrop from v5.1.0 to v5.2.0, stopped the datacubes or nested IDS job.

  This schema integrity check is now turned off. Breaking schema changes, such as a changed column type or a dropped column, still stop the job, but they now appear as write errors. No data is written when this happens.

  This change doesn't affect the Schema Validation option in the ids-to-lakehouse pipeline configuration, which is a separate schema integrity check.

• Reprocessing an ids-to-lakehouse pipeline no longer creates duplicate records in the datacubes_index Lakehouse table. Previously, duplicates could appear when the datacubes merge_operation Advanced Setting was changed to merge_with_update on a pipeline that had already processed files with the default setting, and one of those files was reprocessed. The datacubes table itself wasn't affected. Duplicate index records are removed the next time their file is processed.

Data Access and Management Bug Fixes

• The Health Monitoring dashboard no longer shows disabled Tetra Agents as CRITICAL. Previously, Agents that were disabled, including Agents disabled years earlier, could appear in the Problems list and in the Agents counts with a No CPU metrics available in last 30 minutes message. Enabled Agents that are offline are still reported.

• SQL queries on some Lakehouse tables no longer fail with a TABLE_REDIRECTION_ERROR error. Previously, some of these tables couldn't be queried after they were created, while the matching legacy Athena tables returned results.

• Lakehouse data now appears in the legacy Athena tables in the org_name database shared to Snowflake. Previously, rows for some files were missing from these shared tables, even though the same rows could be queried in Tetra. Tables shared through Databricks weren't affected.

Tetra System Administration Bug Fixes

• Files that encounter an error during registration are now retried. Previously, a failed registration could leave a file record without completing processing (indexing for search, writing to Lakehouse tables, or triggering pipelines), or leave no file record at all, making the file invisible in the platform. The Tetra UI did not report these failures. This issue affected Tetra versions v4.5.0 through v4.5.6, v4.6.0, and v4.6.1.

🚧

IMPORTANT

This fix prevents new files from being affected. Files that were already affected need to be reprocessed. Your customer account leader will reach out to you for remediation if you are impacted.

• File reconciliation jobs that target specific file IDs now recover files that are missing from search results. Previously, these jobs looked up the requested files in search, so a file that was stored in Tetra but missing from search was skipped. The job then finished without creating a repair event for that file and without reporting an error.

• IDS files of a new IDS type or version no longer go missing from search when the search index for that type or version fails to be created.

• In customer-hosted environments, heavy file indexing no longer exceeds the AWS Parameter Store request limit for the account. Previously, exceeding the limit could cause other Tetra services in the same account to drop files.

• Limited availability Data Retention Policies delete files again. In Tetra v4.6.0 and v4.6.1, no retention policy deleted any files, while the policies still appeared healthy and no error was shown. If you rely on retention policies, check for files that should have been deleted during that period.

• For organizations with Data Access Rules turned on, label value suggestions appear again when users add labels to files, uploads, or Agents, or open Label Details. In Tetra v4.6.0 and v4.6.1, the suggestion list was empty for these users. For API users, the GET /v2/fileinfo/label-fields/{labelKey}/assignedValues endpoint no longer returns a 400 error.

Data Apps and Scientific Workspace Bug Fixes

• Direct links to a Data App's subdomain URL now open the app. Previously, a direct link returned a 403 error until the user had opened the app once from its tile in the Data & AI Workspace. Now, Tetra signs the user in if needed, offers to switch to the organization that owns the app if it's another of the user's organizations, and then opens the app on the page the link points to.

Deprecated Features

The following features are now deprecated.

Vocabulary Management Beta

The beta vocabulary management functionality introduced in TDP v4.5.0 is deprecated. It's planned to be reintroduced in an upcoming Tetra release.

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

Known and Possible Issues

The following are known and possible issues for Tetra v4.6.2.

📘

NOTE

No new known issues were introduced in this release. The known issues listed below were also present in previous versions.

Data Integrations Known Issues

• Exceptionally large Tetra Agent audit trail entries can still fail to be processed, in which case the entry doesn't appear in the Tetra audit trail. Tetra v4.6.1 significantly increased the size of the entries that can be processed, and the largest entries observed to date are processed as expected.
• For new Tetra Agents set up through a Tetra Data Hub and a Generic Data Connector (GDC), Agent command queues aren't enabled by default. However, the Tetra UI still displays the command queue as enabled when it's deactivated. As a workaround, customers can manually sync the Tetra Data Hub with Tetra. A fix for this issue is in development and testing and is scheduled for a future release.

Data Harmonization and Engineering Known Issues

• Under heavy load, uploading a large number of IDS files may produce a 504 Gateway Timeout on /api/v1/artifacts/ids/*.
• OpenSearch indexing throughput may be reduced compared to 4.4.x in some environments; further optimization is ongoing.
• Some glue jobs and Lakehouse Delta tables may require re-registration steps following disaster recovery procedures.
• For customers using proxy servers to access Tetra, Tetraflow pipelines created in Tetra v4.3.0 and earlier fail and return a CalledProcessError error. As a workaround, customers should disable any existing Tetraflow pipelines and then enable them again. A fix for this issue is in development and testing and is scheduled for a future release.
• The legacy ts-sdk put command to publish artifacts for Self-service pipelines (SSPs) returns a successful (0) status code, even if the command fails. As a workaround, customers should switch to using the latest TetraScience Command Line Interface (CLI) and run the ts-cli publish command to publish artifacts instead.
• IDS files larger than 2 GB are not indexed for search.
• The Chromeleon IDS (thermofisher_chromeleon) v6 Lakehouse tables aren't accessible through Snowflake Data Sharing. There are more subcolumns in the table's method column than Snowflake allows, so Snowflake doesn't index the table. A fix for this issue is in development and testing and is scheduled for a future release.
• Empty values in Amazon Athena SQL tables display as NULL values in Lakehouse tables.
• File statuses on the File Processing page can sometimes display differently than the statuses shown for the same files on the Pipelines page in the Bulk Processing Job Details dialog. For example, a file with an Awaiting Processing status in the Bulk Processing Job Details dialog can also show a Processing status on the File Processing page. This discrepancy occurs because each file can have different statuses for different backend services, which can then be surfaced in Tetra at different levels of granularity. A fix for this issue is in development and testing.
• Logs don't appear for pipeline workflows that are configured with retry settings until the workflows complete.
• Files with more than 20 associated documents (high-lineage files) do not have their lineage indexed by default. To identify and re-lineage-index any high-lineage files, customers must contact their CSM to run a separate reconciliation job that overrides the default lineage indexing limit.
• OpenSearch index mapping conflicts can occur when a client or private namespace creates a backwards-incompatible data type change. For example: If doc.myField is a string in the common IDS and an object in the non-common IDS, then it will cause an index mapping conflict, because the common and non-common namespace documents are sharing an index. When these mapping conflicts occur, the files aren't searchable through the Tetra UI or API endpoints. As a workaround, customers can either create distinct, non-overlapping version numbers for their non-common IDSs or update the names of those IDSs.
• File reprocessing jobs can sometimes show fewer scanned items than expected when either a health check or out-of-memory (OOM) error occurs, but not indicate any errors in the UI. These errors are still logged in Amazon CloudWatch Logs. A fix for this issue is in development and testing.
• File reprocessing jobs can sometimes incorrectly show that a job finished with failures when the job actually retried those failures and then successfully reprocessed them. A fix for this issue is in development and testing.
• File edit and update operations are not supported on metadata and label names (keys) that include special characters. Metadata, tag, and label values can include special characters, but it's recommended that customers use the approved special characters only. For more information, see Attributes.
• The File Details page sometimes displays an Unknown status for workflows that are either in a Pending or Running status. Output files that are generated by intermediate files within a task script sometimes show an Unknown status, too.
• Some historical protocols and IDSs are not compatible with the new ids-to-lakehouse data ingestion mechanism. The following protocols and IDSs are known to be incompatible with ids-to-lakehouse pipelines:
  • Protocol: fcs-raw-to-ids < v1.5.1 (IDS: flow-cytometer < v4.0.0)
  • Protocol: thermofisher-quantstudio-raw-to-ids < v5.0.0 (IDS: pcr-thermofisher-quantstudio < v5.0.0)
  • Protocol: biotek-gen5-raw-to-ids v1.2.0 (IDS: plate-reader-biotek-gen5 v1.0.1)
  • Protocol: nanotemper-monolith-raw-to-ids v1.1.0 (IDS: mst-nanotemper-monolith v1.0.0)
  • Protocol: ta-instruments-vti-raw-to-ids v2.0.0 (IDS: vapor-sorption-analyzer-tainstruments-vti-sa v2.0.0)
• On the File Processing page, selecting a pipeline that has a very large number of workflows (tens of thousands or more) can take several minutes to load its workflow list, or the list might not load. Pipeline processing isn't affected, and workflows continue to run as expected. A fix for this issue is in development and testing and is scheduled for a future release.

Data Access and Management Known Issues

• High file-upload event latency may occur in some environments, delaying events shown on Health Monitoring pages.
• Data App providers may exhibit the following issues when shared secrets are configured using the Custom provider option:
  • Existing secrets linked to a provider can appear blank or fail to resolve correctly.
  • New secrets created through the Custom provider option on the Providers page can appear as duplicate entries on the Shared Settings page. Do not delete these entries.
    To avoid these issues when using the Custom provider option, create shared secrets on the Shared Settings page using all-lowercase names, and reference them as existing secrets in the provider rather than creating new secrets directly from the Providers page. If you encounter duplicate secret entries or secrets that fail to resolve, contact your customer account leader for assistance. A fix for these issues is in development and testing and is scheduled for a future release.
• When creating a direct-to-lakehouse pipeline (v0.2.0) and selecting an Instant Start (Lambda) option from the Memory Allocation list, the workflow fails and returns a FileNotFoundError: [Errno 2] No such file or directory error. This error is caused by a limitation of the Lambda runtime environment. As a workaround, customers should select a non-Instant Start memory allocation option when configuring a direct-to-lakehouse pipeline. A fix for this issue is in development and testing and is scheduled for a future release.
• When creating a direct-to-lakehouse pipeline, the pipeline won't create the transform output tables if any line breaks (\n), trailing whitespaces, or other special characters are included in the transform output's schemaIdentifier field.
• When using the SQL Search page to query a table created from a direct-to-lakehouse pipeline, the Select First 100 Rows functionality sometimes defaults to an invalid query and displays the following error: "COLUMN_NOT_FOUND: line <number>. Column 'col' cannot be resolved or requester is not authorized to access requested resources." As a workaround, customers should adjust their queries to a standard SELECT * or SELECT column_name query, and then choose the SELECT First 100 Rows option again.
• On the Search (Classic) page, shortcuts created in browse view also appear in collections and as saved searches when they shouldn't.
• Saved Searches created on the Search (Classic) page can't be used or saved as Collections on the Search page.
• Data Apps won't launch in customer-hosted environments if the private subnets where Tetra is deployed are restricted and don't have outbound access to the internet. As a workaround, customers should enable the following AWS Interface VPC endpoint in the VPC that Tetra uses: com.amazonaws.<AWS REGION>.elasticfilesystem
• In deployments where the UI and API use different subdomain hierarchies (for example, frontend.domain.com and api.domain.com instead of api.frontend.domain.com), Data Apps may return CORS errors.
  To resolve, create the following AWS Systems Manager (SSM) parameters:
• /tetrascience/production/ECS/ts-service-data-apps/DOMAIN — Set this to your Tetra URL without https:// (for example, frontend.domain.com). This configures the CORS policy to restrict which origins can send requests to the Data Apps service.
• /tetrascience/production/ECS/ts-service-data-apps/COOKIE_DOMAIN — Set this to the shared root domain (for example, domain.com). This ensures cookies are scoped correctly when the UI and API are on sibling subdomains.
• The Data Lakehouse Architecture doesn't support restricted, customer-hosted environments that connect to Tetra through a proxy and have no connection to the internet. A fix for this issue is in development and testing and is scheduled for a future release.
• On the File Details page, related files links don't work when accessed through the Show all X files within this workflow option. As a workaround, customers should select the Show All Related Files option instead. A fix for this issue is in development and testing and is scheduled for a future release.
• When customers upload a new file on the Search page by using the Upload File button, the page doesn't automatically update to include the new file in the search results. As a workaround, customers should refresh the Search page in their web browser after selecting the Upload File button. A fix for this issue is in development and testing and is scheduled for a future Tetra release.
• Values returned as empty strings when running SQL queries on SQL tables can sometimes return Null values when run on Lakehouse tables. As a workaround, customers using the Data Lakehouse Architecture should update any SQL queries that specifically look for empty strings to instead look for both empty string and Null values.
• Query DSL queries run on indices in an OpenSearch cluster can return partial search results if the query puts too much compute load on the system. This behavior occurs because the OpenSearch search.default_allow_partial_result setting is configured as true by default. To help avoid this issue, customers should use targeted search indexing best practices to reduce query compute loads. A way to improve visibility into when partial search results are returned is currently in development and testing and scheduled for a future Tetra release.
• Text within the context of a RAW file that contains escape (\) or other special characters may not always index completely in OpenSearch. A fix for this issue is in development and testing, and is scheduled for an upcoming release.
• If a data access rule is configured as [label] exists > OR > [same label] does not exist, then no file with the defined label is accessible to the Access Group. A fix for this issue is in development and testing and scheduled for a future Tetra release.
• File events aren't created for temporary (TMP) files, so they're not searchable. This behavior can also result in an Unknown state for Workflow and Pipeline views on the File Details page.
• When customers search for labels in the Tetra UI's search bar that include either @ symbols or some unicode character combinations, not all results are always returned.
• The File Details page displays a 404 error if a file version doesn't comply with the configured Data Access Rules for the user.

Data Apps and Scientific Workspace Known Issues

• Two installs of the same data app slug under two different namespaces of the same type (for example, two private-* namespaces) currently collide on the subdomain key, and the second install fails. A fix for this issue is in development and testing and is scheduled for Tetra v4.8.0.

• In some installations, the Gallery tile in the Data & AI Workspace and the Data App details page may display different installed-version strings for the same Data App. If they disagree, the version shown on the Data App details page is correct; the Gallery tile may show an earlier version during or shortly after an upgrade. A fix for this issue is in development and testing and is scheduled for Tetra v4.8.0.

Tetra System Administration Known Issues

• Timeout issues may occur with the /v1/organizations endpoint under heavy automation load.
• The AI Platform App "upload supporting files" button may not work in environments where the required AI Runtime Services are unavailable.
• Limited availability release Data Retention Policies don't consistently delete data. A fix for this issue is in development and testing and is scheduled for a future release.
• Failed files in the Data Lakehouse can't be reprocessed through the Health Monitoring page. Instead, customers should monitor and reprocess failed Lakehouse files by using the Data Reconciliation, File Processing, or Workflow Processing pages.
• The latest Connector versions incorrectly log the following errors in Amazon CloudWatch Logs:
  • Error loading organization certificates. Initialization will continue, but untrusted SSL connections will fail.
  • Client is not initialized - certificate array will be empty
    These organization certificate errors have no impact and shouldn't be logged as errors. A fix for this issue is currently in development and testing, and is scheduled for an upcoming release. There is no workaround to prevent Connectors from producing these log messages. To filter out these errors when viewing logs, customers can apply the following CloudWatch Logs Insights query filters when querying log groups. (Issue #2818)
    CloudWatch Logs Insights Query Example for Filtering Organization Certificate Errors

  fields @timestamp, @message, @logStream, @log
  | filter message != 'Error loading organization certificates. Initialization will continue, but untrusted SSL connections will fail.'
  | filter message != 'Client is not initialized - certificate array will be empty'
  | sort @timestamp desc
  | limit 20

• If a reconciliation job, bulk edit of labels job, or bulk pipeline processing job is canceled, then the job's ToDo, Failed, and Completed counts can sometimes display incorrectly.

Upgrade Considerations

During the upgrade, there might be a brief downtime when users won't be able to access the Tetra user interface and APIs.

After the upgrade, the TetraScience team verifies that the platform infrastructure is working as expected through a combination of manual and automated tests. If any failures are detected, the issues are immediately addressed, or the release can be rolled back. Customers can also verify that Tetra search functionality continues to return expected results, and that their workflows continue to run as expected.

For more information about the release schedule, including the GxP release schedule and timelines, see the Product Release Schedule.

For more details on upgrade timing, customers should contact their customer account leader.

Security

TetraScience continually monitors and tests the Tetra codebase to identify potential security issues. Various security updates are applied to the following areas on an ongoing basis:

• Operating systems
• Third-party libraries

This release also includes security fixes across platform services. These fixes remove credentials and other sensitive values from the logs of several platform services and from build artifacts, strengthen authentication and organization isolation checks, and remove an unused API route. No customer action is required.

Quality Management

TetraScience is committed to creating quality software. Software is developed and tested following the ISO 9001-certified TetraScience Quality Management System. This system ensures the quality and reliability of TetraScience software while maintaining data integrity and confidentiality.

Other Release Notes

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