Release date: 2 September 2026 (updated 3 September 2026)

TetraScience released Tetra version 4.6.0. This release focuses on platform scalability and observability, expanded health monitoring and alerting, and a significant cost-optimized refresh of the data app infrastructure.

Key Updates

• Improved Lakehouse job observability: reduce troubleshooting time with cluster, compute, and cost metrics surfaced per job run.
• Performance optimizations for Lakehouse pipelines: get more predictable pipeline runtimes and fewer out-of-memory failures.
• Search indexing scalability: ingest at larger scale without indexing becoming the bottleneck.
• Auto-shutdown of inactive Data Apps: cut compute spend by disabling idle apps instead of deleting them.
• Faster Data App load times: start apps quicker and avoid cross-environment auth cookie conflicts.
• Customer-facing ingestion alerts: find out when data stops flowing before your scientists do, with alerts for missed uploads, throughput drops, latency breaches, and scan-duration anomalies.
• Tetra Data key/value search in the new Search experience: filter by IDS file content in the new interface, closing the main remaining gap with Classic Search, which is removed in this release.

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

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

New functionalities are features that weren't previously available in Tetra.

Data Access and Management New Functionality

Customer-Facing Alerting for Data Ingestion

Tetra now supports configurable alerts for data ingestion health, so administrators can be notified proactively when data flow degrades. New alert types include:

• File uploads below threshold — fires when an Agent stops sending data within an expected window (no heartbeat or file uploads).
• Ingestion throughput drop — fires when the file/record ingest rate falls significantly below baseline (for example, a 50% drop in 15 minutes).
• High ingestion latency (time-to-platform) — fires when end-to-end latency from Agent file upload to data being queryable exceeds an SLA threshold.
• Per-agent / per-project scan duration anomaly — fires when a specific Agent's project scan takes abnormally long compared to its historical baseline.

The Alert Management page has been updated to include these new alert types, so administrators can configure and subscribe to them alongside existing Tetra Agent, Tetra Connector, and Tetra Hub alerts.

Data Integrations New Functionality

Connector Details Page Recent Logs Tab

Individual connector details pages now include a tab for recent logs, making connector logs easier to access without needing direct infrastructure access.

File Log Agent (FLA) Configuration Enhancements

The FLA Configuration tab adds a new search capability for paths and path attributes, helping determine instrument connectivity or identify duplicate path configurations.

Data Harmonization and Engineering New Functionality

Lakehouse Job Observability and Metrics

Lakehouse Databricks (DBX) job monitoring now surfaces richer cluster, compute, and cost metrics through the Tetra platform, beyond the previous run-level attributes (state, duration, error messages).

Tetra System Administration New Functionality

Org Admin Audit Trail Toggle Feature Flag

A new platform-level feature flag controls whether the Audit Trail on/off toggle is exposed to Org Admins in Tetra Org Settings. For regulated GxP organizations, this lets TetraScience ensure the audit trail remains permanently enabled and non-configurable by Org Admins.

Fullscreen Mode for Data Apps

Data app users can now toggle a fullscreen mode that hides the top toolbar and left navigation, both in the Scientist Experience view and in the Build and Manage (IT Mode) view, for a more focused app experience.

IDS Key/Value Search in the New Search Experience

The new Search experience now supports IDS key/value (Data) filters, allowing users to search IDS files by specifying key/value pairs from file content and to add instruments matching the IDS schema to saved searches. This brings the capability previously only available in Classic Search into the new interface.

Job Monitor Page Summary and Duration Graph

The Job Monitor page now includes a header summary section and a Job Run duration graph with updated statistics for Lakehouse and inferencing jobs, giving better at-a-glance observability of job activity.

Data Apps and Scientific Workspace New Functionality

Serverless/Server Data App Convergence

Serverless apps and container Data Apps are converging into a single unified "Data App" concept. Serverless data apps are now served from the Artifact Management Service (ArMS) as module-federation-loaded artifacts (including dist.zip and manifest serving and an on-read unzip endpoint), routed end-to-end through ts-service-web and Data Acquisition. A unified data app cookiecutter template supports conditional serverless/server generation, and the ts-cli publish flow and the data app catalog have been updated accordingly.

Disable and Auto-Shutdown of Inactive Data Apps

Data apps can now be "disabled" (running ECS task count set to zero) instead of hard-deleted, and inactive data apps can be automatically shut down to reduce costs.

Deterministic Data App Routing and Query Parameter Forwarding

Data apps can now be reached through a deterministic, path-based endpoint (for example, /dataapps/apps/{app-slug}/), and parent page URL query parameters are forwarded to the data app iframe.

Pre-Release Artifact Support for Data Apps and Connectors

Data app and connector artifacts now support pre-releases, allowing developers to test specific beta versions before general availability.

Enhancements

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

Data Access and Management Enhancements

Hardened Cloud Hub Solution

The Cloud Hub (the standalone proxies that give customers a single egress point for agent and connector connections) is now hardened and operationally improved:

• Cloud Hubs are created in the platform CloudFormation stack and auto-upgraded with the platform.
• Proxies are network-restricted with a restrictive whitelist allowing access only to required Tetra AWS endpoints, with VPC endpoints and no internal access.
• PrivateLink endpoints are now cross-regional, removing the need for separate hubs per region.
• Cloud Hub offline alarms are sent to the Tetra alarm SNS, and the whitelist is configurable by stack parameter.

Data Integrations Enhancements

Search File-Log Agent Paths in the Tetra UI

You can now search the file-monitoring paths configured for a Tetra File-Log Agent (FLA) directly in the Tetra UI. A search bar above the path configuration lets you search a single Agent's paths by Path (scan folder path), Labels (both name and value), Patterns, and Source Type, so you can confirm that paths are configured consistently, identify duplicate paths, and verify that all expected instrument paths are present. Search is available for both locally managed and cloud managed Agents, whether the Agent is online or offline, and before you save the final configuration to the Agent (including paths you've edited or added but not yet saved). When more than 10 entries match, the results are paginated until you clear the search.

Data Harmonization and Engineering Enhancements

Spark Optimizations to Prevent Data Skew and OOM

Lakehouse direct-to-lakehouse processing pipelines have been optimized to reduce unpredictable execution times and recurring stability issues such as out-of-memory errors and disk spills. This includes collecting record counts and data statistics (number of files, total file size) and passing them to Databricks jobs to improve Spark performance, with corresponding updates to the IDS, Datacubes, and Direct Lakehouse artifacts to include record counts in staging file names.

Tetra System Administration Enhancements

OpenSearch Indexing Scalability and Throughput

To better enable large-scale ingestion, the OpenSearch service has been redesigned to address throughput bottlenecks.

Optimized UI API Calls and Pagination

Tetra UI has been optimized to reduce eager loading and implement pagination and server-side typeahead for large datasets.

IT Mode Design Refresh and Dark Mode

Tetra's IT Mode (Build and Manage) has been restyled with the new design language and design tokens, including a refreshed error page and dark mode support. When in dark mode, a banner warns when a platform app (AI Platform, Scientist Experience, Artifact Version Manager) does not yet support dark mode.

Classic Search Removal

Classic Search is removed in Tetra v4.6.0. Tetra displays a banner notifying users that Classic Search has been sunsetted, and the page is hidden behind a CLASSIC_SEARCH feature flag (hidden by default). As a temporary transition measure, organizations that still need Classic Search can contact their customer account leader to have the flag enabled. For more information, see Tetra Product Deprecation Notices.

Preserve Pipeline Retry Behavior on Protocol/Version Change

When you change the protocol or protocol version of an existing pipeline, your configured retry behavior is now preserved unless the new protocol schema is incompatible.

Search API Label Validation Type

File and search API responses now include the validationType for label data, supporting the move away from caching all labels in the UI at startup.

Data Apps and Scientific Workspace Enhancements

Data App Performance Enhancements

Data app performance and time-to-load have been improved, including resolving shared root-domain cookie conflicts (by isolating data app auth cookies per Tetra environment), enabling SOCI image indexing for faster container startup, and server-side pagination and search in the artifact management API. A gateway payload limit for executeDML was raised to 5MB to fix 413 errors on managed-table bulk writes.

Data App and AI Workspace UI Improvements

The Data & AI Workspace experience has been polished, including:

• Showing the data app Details/Overview to non-admin users on the Dashboard tab.
• Displaying a Last Updated timestamp on each data app tile and in the gallery.
• Consolidating the platform requirements vs. service requirements UI.

Infrastructure Updates

The following is a summary of the Tetra infrastructure changes made in this release. For more information about specific resources, contact your customer account leader.

• A new ts-service-data-apps-proxy service with dedicated ALB target group and listener rules.
• A new health monitoring backend and event metrics extractor Lambda.
• Cloud Hub proxies created and auto-upgraded within the platform CloudFormation stack, with cross-regional PrivateLink endpoints.
• Lambda Authorizer and AWS API Gateway integration as part of the gateway migration.
• OpenSearch ISM rollover enablement and monitoring.

Bug Fixes

The following bugs are now fixed.

Data Access and Management Bug Fixes

• Fixed the Purge Pending Commands page so the "All Targets" item could not be incorrectly listed, and widened the target selection dropdown.
• Fixed Operational Insights dashboard errors caused by missing PHT tables on new orgs and invalid Glue schema errors for the Agent Files Uploaded table.

Data Integrations Bug Fixes

• Fixed GET /v1/agents randomly failing with a 504 Gateway Timeout.

• Large Tetra Agent audit trail entries are now processed reliably. Previously, audit trail entries that grew to several megabytes (which can occur when an Agent monitors a large number of projects or paths, because each configuration change adds to the audit record) could cause audit trail processing to run out of memory. When this happened, the audit trail object was stored but never marked as processed, so the entry didn't appear in the Tetra audit trail and no error was surfaced to customers.

Data Harmonization and Engineering Bug Fixes

• Fixed multiple Lakehouse job issues where pipelines appeared successful in Tetra but failed in Databricks, including unreachable clusters and silent direct-to-lakehouse failures.
• Fixed direct-to-lakehouse schema evolution not applying to new columns.
• Fixed job duration on the Health Monitoring page incorrectly including queue time, and the cache enable/disable setting not being respected for IDS and Normalized IDS jobs.

Tetra System Administration Bug Fixes

• Fixed users with Active Directory groups containing special characters (including spaces) being unable to log in.
• Fixed filename substring search not working as expected and the query optimizer causing extreme shard fan-out when filtering only on document-level metadata fields.
• Fixed personal tokens triggering a user token refresh that could result in logout.
• Fixed File Details showing a 404 page for deleted files and "failed to load folders" after a new file upload in a new org.
• Fixed pipelineBulkProcessing reprocess failures caused by stale/corrupted search_after cursors.
• Removed auth tokens from Artifact Management service logs.

Data Apps and Scientific Workspace Bug Fixes

• Fixed the Audit Trail not logging when a data app is uninstalled.
• Fixed the data app "Upgrade" button missing for the Developer role on the data app details page.
• Fixed GET /v1/dataapps/apps/manage returning duplicate app entries when artifactType and slug collide across namespaces or versions.
• Fixed the data apps proxy not issuing ts-auth-token/x-org-slug Set-Cookie on seed-fetch responses (iframe loads returning 403).
• Fixed GET /v1/dataapps/providers/templates returning 503 and a backfill job failing with 401.
• Fixed SWR cache not being invalidated on provider deletion (causing 503 on app manage) and Data & AI Workspace layout issues.

Deprecated Features

Classic Search, deprecated since Tetra v4.4.0, is removed in Tetra v4.6.0. Tetra displays a banner notifying users that Classic Search has been sunsetted, and the page is hidden behind the CLASSIC_SEARCH feature flag (hidden by default). As a temporary transition measure, organizations that still need Classic Search can contact their customer account leader to have the flag enabled. Customers should migrate to the Search page.

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

Last updated: 3 September 2026

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. A further fix for this issue is in development and testing and is scheduled for a future release.
• 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.
• For on-premises standalone Connector deployments that use a proxy, the Connector's installation script fails when the proxy's name uses the following format: username:password@hostname. As a workaround, customers should contact their customer account leader to update the Connector's install script. 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)

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.
  • Upgrading a data app after deleting a provider can return a 503 error. As a workaround, do a hard refresh in your browser and retry the upgrade.
    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. Do a hard refresh in your browser after any provider changes, especially deletion. 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

• Users with the Developer or Analyst policy can't attach an existing provider to a data app in the Data & AI Workspace. This limitation affects the UI only; there is no change to the API. As a workaround, a user with data app edit access can attach providers by calling the /v1/dataapps/apps/manage endpoint directly with the providerIds list for the data app. A fix for this issue is in development and testing and is scheduled for Tetra v4.6.1.

• Users with the Data Owner policy don't see the Sessions tab on the details page for an embedded data app. There is no workaround. A fix for this issue is in development and testing and is scheduled for Tetra v4.6.1.

• Users with the Developer or Analyst policy don't see the Attribute Management tab on the details page for an embedded data app, so they can't apply labels to it. The tab is available for linked data apps. There is no workaround. A fix for this issue is in development and testing and is scheduled for Tetra v4.6.1.

Tetra System Administration Known Issues

• The org deletion task script may not fully delete an org after multiple attempts in some cases.
• 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.
• The Data user policy doesn't allow users who are assigned the policy to create saved searches, even though it should grant the required functionality permissions.
• 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

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.