API ReferenceDocumentation
Documentation

Tetra Egnyte Connector v1.x Release Notes

The following are the release notes for Tetra Egnyte Connector versions 1.x, which is an improved version of the Legacy Egnyte Connector. It is a standalone, containerized application that uses the Pluggable Connector Framework to monitor Egnyte software folders for new and modified files, and then upload them to Tetra.

v1.1.0

Release date: 05 August 2026

TetraScience has released its newest general availability (GA) version of the Tetra Egnyte Connector, v1.1.0. The Connector is a standalone, containerized application that uses the Pluggable Connector Framework to monitor Egnyte software folders for new and modified files, and then upload them to Tetra.

This release: allows the Connector to use refresh tokens for automated reauthentication with Egnyte; adds additional logging of all Egnyte events seen by the Connector; adds support for file move or file rename events in Egnyte; fixes several other bugs

Prerequisites

Tetra Egnyte Connector v1.1.0 requires the following:

  • Active Egnyte account
  • A valid client ID and client secret for an app defined in the Egnyte developer portal (contact your customer account leader to get help setting this up)
  • Access to an Egnyte login with sufficient permissions to ingest files

New Functionality

New functionality includes features not previously available in earlier versions of the Connector.

Support for Renaming or Moving Egnyte Files

The Connector can now handle Egnyte events corresponding to renaming or moving Egnyte files. Files that are moved or renamed have the path matching filters applied to both the source and destination paths, and will be ingested if any match. Similarly, decisions about labels or metadata-only status are based on all matching paths.

Rename / move support is enabled by default in the Connector. If you wish to opt out, a new toggle in the configuration window allows you to disable support for renaming / moving.

Enhancements

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

Automated reauthentication with Egnyte

The Connector now obtains a refresh token from Egnyte. When the access token is within 24 hours of expiry, the Connector will exchange the refresh token for a new one, setting a critical health status only if that fails. Note: to use the new refresh token, you will need to perform manual authentication of the connector once after upgrading to v1.1.0.

Additional file labels

For all uploads, the Connector now affixes labels with the last modified time in Egnyte and the Egnyte event ID associated with an upload. This simplifies the task of checking if Tetra version order looks consistent with Egnyte version order (see Limitations)

Bug fixes

The following bugs are now fixed:

  • A bug where files with no contents would always fail checksum comparison has been fixed.
  • In version 1.0.0, if a file in Egnyte goes through multiple version changes before the connector has seen the associated events, the connector will mistakenly ingest the file (or associated metadata) associated with the latest version only for all of these events. This shows up as the file having multiple versions in Tetra, but all corresponding to the same, latest Egnyte version. This issue is resolved in version 1.1.0.
  • When successfully reauthenticating, the connector will now immediately clear any non-HEALTHY health status associated with previous auth problems.

Limitations

The following are known limitations for Tetra Egnyte Connector v1.1.0:

  • The Authentication tab only works for Tetra users with admin privileges.
  • You can't use shared settings for the client-id.
  • When rename events are allowed, you may end up with duplicate versions of files in Tetra if you repeat names. For example, if file_A is renamed to file_B and then back to file_A with no other changes, Tetra will show multiple versions of the file although nothing has changed. The Egnyte entry_id can be used to distinguish among Egnyte file versions.
  • The Connector makes a best effort to ensure that versions of an uploaded file appear in Tetra in the same order that they do in Egnyte. However, the event processing order in Tetra is not guaranteed and this may result in version order mismatch between Tetra and Egnyte. This is most likely to occur when the connector is processing uploads of multiple versions of a file in a single batch. The Connector now attaches labels containing the Egnyte last modified timestamp and the event ID corresponding to the upload to allow you to catch cases where this occurs.

Deprecated Features

  • The command TetraScience.Connector.Egnyte.MarkFileSkipped.v1 has been replaced with TetraScience.Connector.Egnyte.MarkFileSkipped.v2

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

Known and Possible Issues

There are no known issues for Tetra Egnyte Connector v1.1.0.

Upgrade Considerations

Customers can upgrade directly to Tetra Egnyte Connector v1.1.0 from earlier versions of the Connector.

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

For more information, see the Tetra Egnyte Connector User Guide (v1.x).

Other Release Notes

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

v1.0.0

Release date: 10 December 2025 (updated 31 July 2026)

TetraScience has released its first general availability (GA) version of the Tetra Egnyte Connector, v1.0.0, which was previously in beta release and is an improved version of the Legacy Egnyte Connector. The Connector is a standalone, containerized application that uses the Pluggable Connector Framework to monitor Egnyte software folders for new and modified files, and then upload them to Tetra.

This release introduces a custom command to mark files as skipped and provides improved configuration validation for polling intervals. It also fixes a bug related to metadata-only file path validation.

Prerequisites

Tetra Egnyte Connector v1.0.0 requires the following:

  • Active Egnyte account
  • A valid client ID and client secret for an app defined in the Egnyte developer portal (contact your customer account leader to get help setting this up)
  • Access to an Egnyte login with sufficient permissions to ingest files

New Functionality

New functionality includes features not previously available in the Tetra Egnyte Connector beta release version.

Mark File as Skipped Command

The Connector now supports a custom command (TetraScience.Connector.Egnyte.MarkFileSkipped.v1) to mark specific file versions as SKIPPED, preventing them from being processed. Skipping file versions can be useful in any of the following situations:

  • Skipping corrupted or invalid files
  • Excluding files that should not be processed
  • Temporarily skipping files pending fixes or updates

The command can be sent via the TetraScience Command Service or through the Connector's page in the Tetra user interface. The skip reason is stored in file metadata for audit purposes.

For more information, see Custom Commands in the Tetra Egnyte Connector User Guide (v1.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.

Improved Polling Interval Validation

The Connector now validates that the polling interval is between 1 and 1440 minutes (24 hours) at configuration time. It also provides clearer error messages when invalid values are provided.

For more information, see Configuration Parameters in the Tetra Egnyte Connector User Guide (v1.0.x).

Bug fixes

The following bugs are now fixed:

  • Metadata-only file paths are now tested against the original filename when matching path configurations, rather than the .index.json filename.

Limitations

The following are known limitations for Tetra Egnyte Connector v1.0.0:

  • The Authentication tab only works for Tetra users with admin privileges.
  • Added 16 July 2026: the token from Egnyte expires every 30 days. The connector will show a WARNING health status beginning two days before expiry. The connector must be reauthorized. Upcoming versions of the connector will employ a refresh token to address this.
  • You can't use shared settings for the client-id.

Deprecated Features

There are no deprecated features in this release.

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

Known and Possible Issues

  • Added 31 July 2026: if a file in Egnyte goes through multiple version changes before the connector has seen the associated events, the connector will mistakenly ingest the file (or associated metadata) associated with the latest version only for all of these events. This shows up as the file having multiple versions in Tetra, but all corresponding to the same, latest Egnyte version. This issue is resolved in version 1.1.0.

Upgrade Considerations

Customers can upgrade directly to Tetra Egnyte Connector v1.0.0 from the Tetra Egnyte Connector beta release version.

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

For more information, see the Tetra Egnyte Connector User Guide (v1.0.x).

Other Release Notes

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

Updated 8 days ago

Did this page help you?