The following are the Tetra Chromeleon Agent release notes for versions 2.3.x.

v2.3.0

Release date: 9 January 2026

TetraScience has released its next version of the Tetra Chromeleon Agent version 2.3.0. This release introduces several enhancements to sequence creation commands, improved data integrity with SHA1 checksums for Amazon Simple Storage Service (Amazon S3) uploads, and multiple bug fixes to improve stability and performance.

Prerequisites

The following Tetra Data components are required for Tetra Chromeleon Agent v2.3.0:

📘
NOTE
Documentation for Tetra Data components is in the TetraConnect Hub. To request access, see Access the TetraConnect Hub.

Tetra Data:
- IDS: Chromeleon IDS (thermofisher-chromeleon) v7.0.0
  - Protocol: chromeleon-raw-to-ids v5.0.1
  - Task script: chromeleon-raw-to-ids v8.0.1
- IDS: Thermofisher Chromeleon Reports (thermofisher-chromeleon-reports) v1.0.0
  - Protocol: thermofisher-chromeleon-reports v1.2.0
  - Task script: thermofisher-chromeleon-reports v1.2.0

New Functionality

New Functionality includes features not previously available in the Tetra Chromeleon Agent.

There is no new functionality in this release.

Enhancements

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

The eWorkflow Creation command now supports an optional FailWhenPathNotExist parameter in the payload. When set to true, the Agent verifies that the specified sequence folder path exists before creating the sequence. This enhancement helps prevent sequences from being created in unexpected locations.
The eWorkflow Creation command now validates that the default path configured in the eWorkflow matches the path specified in the command payload (when SDK version is 7.2.9 or higher). If the paths do not match, the command fails to prevent sequences from being created in unintended locations. This validation is particularly important in highly regulated GxP environments.
The Sequence Creation (Worklist) command now supports an optional FailWhenPathNotExist parameter in the payload. When set to true, the Agent verifies that the specified sequence folder path exists before creating the sequence. If the folder does not exist, the command fails and returns an error message. This enhancement provides better control over folder structure management in regulated environments.
The Sequence Creation (Worklist) command now returns detailed sequence information in the success response payload, including the full sequence URL, name, custom fields, and injection details. This information provides better visibility into the created sequence.
When uploading text-based reports generated from Report Templates, the Agent now includes the sequence eSignature status as a label (sequence_esignature_status) with values of submitted, reviewed, or approved. This status value enables pipeline triggers to LIMS or ELN systems based on the signature status of the report.
The Agent now stops services within 30 seconds when the stop command is issued, providing more predictable shutdown behavior.
The Cancel and Skip Server buttons in the Data Vault tab now respond more quickly when scanning data servers, improving the user experience in the Agent Management Console.
The Agent now defaults to using SHA1 checksums for S3 Direct Upload instead of SHA256, which improves upload performance while maintaining data integrity. When S3 Direct Upload isn't activated, the Agent continues to use MD5 checksums for uploads through the connector API to maintain backward compatibility.

Bug Fixes

The following bugs are now fixed:

The Agent now correctly checks if a sequence has a default channel configured before attempting to generate text-based reports from Report Templates, preventing unnecessary report generation errors.
The summary page now correctly excludes canceled injection history items when calculating the total number of generated items. Previously, canceled injections were included in the total count, which could result in the total generated items being larger than the total scanned items, causing confusion. This fix is particularly important when the Agent loses connection to data vaults and injections need to be regenerated.
The Sequence Creation (Worklist) command now correctly maps the Spike Group field when specified in the JSON payload. Previously, this field was not included in the XML mapping, causing the Spike Group to remain empty in the created sequence.
The Agent now correctly handles situations where the Chromeleon database becomes temporarily unreachable. Previously, if the database connection was lost during a scan, the Agent would delete existing sequences from its local database. The Agent now uses a soft delete approach to prevent data loss when the database is temporarily unavailable.
The Agent now correctly handles large batch sizes when passing arguments to child processes. Previously, when the command line arguments exceeded the maximum size allowed by Windows, the process would crash with a "filename or extension is too long" error. The Agent now writes arguments to a temporary file when they exceed 2,000 characters.
The DataVaultSequenceScanCompletedV1Event now correctly reports duration values in seconds rather than milliseconds.
The Agent's SQLite database backup process now correctly includes all committed transactions by performing an explicit checkpoint before uploading the backup to Amazon S3. Previously, the backup could miss recent transactions because of SQLite's write-ahead log (WAL) mode.

Deprecated Features

There are no new deprecated features in this release. For more information about TDP deprecations, see Tetra Product Deprecation Notices.

Known and Possible Issues

The following are known or possible issues in Tetra Chromeleon Agent v2.3.0:

To reduce sequence detection latency, the Agent adds a configuration option that limits detection to sequences created within a specified number of recent days. Sequences created earlier than this period are excluded from change detection. This configuration option is per Data Vault.
Report Templates using Report Templates 2.0 do not render correctly using the Chromeleon SDK. This issue is under investigation with the vendor.
Report Templates with pages which require a Component context do not render correctly when using the Chromeleon SDK. This issue is under investigation with Chromeleon.
Renaming a Report Template that is set as the Default Report Template for a Sequence in Chromeleon will not correctly update the Sequence with the new Report Template name. It will also cause any associated injections to be generated with an empty Report Template. To regenerate these injections after changing the name of a Report Template, you must select the Report Template as the Default Report Template for the Sequence again.
Because of a lack of the sample sequence and injections for testing, the formula used by the following Report Variables is not verified:
- Injection
  - ChemicalFormulaAndAdductMassesSingleLineListUsingInjectionAdducts
  - ChemicalFormulaAndAdductMassesMultiLineListUsingInjectionAdducts
  - ChemicalFormulaAndAdductsSingleLine
  - ChemicalFormulaAndAdductsMultiLine
  - LevelCheck
- Chromatogram
  - MsSignalExtractParameters
    - EvaluationType
- Peak Result
  - AmountDeviationAbsoluteInAmountUnits
  - AmountDeviationRelativeInPercentageOfTheExpectedAmount
  - KValueForDeadTimeStoredInProcessingMethod
  - RelativeAmountForCorrespondingInternalStandardComponent
  - RelativeAmountForCorrespondingReferenceComponent
  - RelativeAreaForCorrespondingInternalStandardComponent
  - RelativeAreaForCorrespondingReferenceComponent
  - RelativeCeAreaForCorrespondingInternalStandardComponent
  - RelativeCeAreaForCorrespondingReferenceComponent
  - RelativeHeightForCorrespondingInternalStandardComponent
  - RelativeHeightForCorrespondingReferenceComponent
  - RelativeRetentionTime
  - ResolutionWithEPFormulaAndPreviousIndentifiedPeak
  - ResolutionWithEPFormulaAndCorrespondingReferenceComponent
  - ResolutionWithEPFormulaAndCorrespondingInternalStandardComponment
  - ResolutionWithUSPFormulaAndPreviousIndentifiedPeak
  - ResolutionWithUSPFormulaAndCorrespondingReferenceComponent
  - ResolutionWithUSPFormulaAndCorrespondingInternalStandardComponment
  - ResolutionWithStatisticalMomentFormulaAndPreviousIndentifiedPeak
  - ResolutionWithStatisticalMomentFormulaAndCorrespondingReferenceComponent
  - ResolutionWithStatisticalMomentFormulaAndCorrespondingInternalStandardComponment
  - RetentionIndexLinear
  - RetentionIndexLogarithmic
- Peak Purity
  - InternalStandardChromatogramChannelName
  - InternalStandardChromatogramDetector
  - InternalStandardPeakName
  - InternalStandardPeakNumber
  - ReferenceMsSpectrumMatch
  - Hit Spectrum
- Peak Fluorescence Spectrum
  - ScanValue2ndGreatestRelativeMaximum
  - ScanValue3rdGreatestRelativeMaximum
  - ScanValue4thGreatestRelativeMaximum
  - ScanValue5thGreatestRelativeMaximum
- Peak Composite
  - IsotopicDotProduct
- Peak Tentative Identification
  - Amount
  - InternalStandardName
    LibraryName
  - Match
  - Name
  - Probability
  - ReverseMatch
- Processing Method
  - BlankRunInjectionName
  - LastFixedCalibrationUpdateOperator
  - LastFixedCalibrationUpdateTime
- Processing Method Component
  - RetentionIndex
- Processing Method Component Detection Parameters
  - BaseLineNoiseStartTime
  - BaseLineNoiseEndTime
  - LockedBaseline
  - MaxAreaReject
  - MaxHeightReject
  - MinBaselineScans
  - PeakShoulderThreshold
  - PeakSliceValue
  - RiderThreshold
  - FrontRidersToMainPeak
  - Sensitivity
  - ValleyToValley
  - VoidVolumeTreatment
- Processing Method Peak Group
  - CurrentInjectionAmount
  - MinAmount
  - MaxAmount
- Processing Method Ms Settings
  - AbsoluteThreshold
  - FixedBaselineCorrectionRangeMaxFor1stFixedRange
  - FixedBaselineCorrectionRangeMaxFor2ndFixedRange
  - FixedBaselineCorrectionRangeMinFor1stFixedRange
  - FixedBaselineCorrectionRangeMinFor2ndFixedRange
- Processing Method Test Case
  - NumberOfFailActions
  - NumberOfPassActions

Upgrade Considerations

To upgrade from a previous Agent version, see Upgrade an Agent and the Tetra Chromeleon Agent Installation Guide (v2.3.x).

To configure and use the Agent after it's installed, see the Tetra Chromeleon Agent User Manual (v2.3.x).