Skip to main content

Release Notes Archive

This archive includes all release notes from the past three months.

Version 3.50.3​

March 25, 2026

Bugs​

Resolved Unauthorized Errors During Message Publishing​

We’ve fixed an issue where messages were not being published to Connectors due to an “Unauthorized” error.

Version 3.50.2​

March 20, 2026

Bugs​

Dashboard Access Restored for Standard Users​

Standard users can now access the dashboard as expected.

Unauthorized Errors Now Use Correct Event Codes​

HTTP 401 errors are now labelled with the correct event code, making them easier to identify and troubleshoot.

Retrying Status Accuracy Improved​

The "pending retrying" count now correctly matches the retry list, including in edge cases.

Version 3.50.0​

March 16, 2026

Features​

Expanded Explore Capabilities​

This release adds expanded capabilities to Explore to provide greater control over your canonical data layer.

The concepts of standard schema and extension schema have been unified. There is no longer a distinction between standard and extension properties.

Tables can now be created and edited directly in Explore.

Tables can now be added to entities.

Records in tables can now be created, edited, and deleted directly from within Explore.

You can now define data types and nullability constraints for data types.

Import/Export Now Uses Name-Based Merging​

Schema imports now use name-based merging. When importing a schema into an environment, elements (shapes, tables, and entities) with the same name are treated as the same object and merged as follows:

Shapes: If a shape with the same name already exists, it will not be updated.

Tables: If a table with the same name already exists, properties from the import file will be added or merged.

Property conflicts: Existing properties with a different data type will not be modified.

Added an Example Prompt for AI Coding Tools​

Added an example prompt for AI coding tools to help produce more consistent results when building SyncHive apps. This prompt is generated when an App Registration is created or updated.

Bugs​

Concurrent ID Resolution Could Create Duplicates​

Fixed an issue where resolving IDs for the same record concurrently could result in duplicate records being created.

Improved filtering of soft-deleted records in Hive Explorer​

Enhanced both the logic and user experience when working with soft-deleted records (isDeleted = true). Users can now clearly choose whether to include or exclude soft-deleted records when viewing all records, and can also filter explicitly by isDeleted = true or isDeleted = false for more precise results.

Improved filter query behavior with null values​

Updated the filtering logic so that when a filter condition is applied (for example, a property does not equal a specific value), records with null values are correctly included in the results when they logically satisfy the query.

Version 3.24.3​

March 4, 2026

Features​

Ability to use External OAuth2 Token Endpoints​

This release adds the ability to use external OAuth2 token endpoints for outbound integrations.

Remove Character Limit on Certificate Authentication Types​

This release removes the character limit (255) on certificate authentications for integrations.

Bugs​

Fix Dashboard Stats Failing to Update Intermittently​

This release fixes a defect with processing updates to the dashboard stats. Certain scenarios was causing the batch processing of the stats to fail, causing other updates in the batch to fail alongside it.

Version 3.24.2​

March 2, 2026

Bugs​

Fix of the Process of Inbound Messages with Long Identifiers​

We’ve fixed an issue with the platform being unable to handle inbound requests which contained identifiers which were too long (integration key, shape, external ID).

Version 3.24.1​

February 18, 2026

Bugs​

Fix Incorrect URLs in Security Discovery API​

Fixed an issue where the security discovery API returned an incorrect URL. This resulted in libraries being unable to discover the correct URLs for authentication.

Version 3.24.0​

February 18, 2026

Features​

SyncHive Apps: Register and Access Data from Your Own Applications​

In v3.24.0, we’re introducing support for SyncHive Apps, empowering teams to register external applications directly with SyncHive and use them to read and write data via our APIs. This update simplifies how users build apps that interact with SyncHive’s Unified Data Store (UDS).

What’s included:

  • App Registration: Users can now register any external application inside SyncHive by providing basic app details (name, shapes it connects to, allowed app URLs, and status). Once registered, SyncHive issues a publishable key your app will use to initialize the SyncHive JavaScript SDK.
  • Manage Apps Easily: Registered apps are listed in the SyncHive Apps UI where you can view connection details, update registration info, toggle status, or delete the app.
  • Requesting Data: After signing in from your app, developers can use helper methods like list(), get(), create(), and update() to interact with shape data stored in SyncHive. Filtering and paging options are also supported in API calls for efficient data retrieval. All data requests are handled through the SyncHive JavaScript SDK, which manages secure user authentication, session handling, and ensures API calls follow SyncHive’s security rules. Access is always tied to authenticated users and approved app settings, providing controlled and auditable data access.

Version 3.23.0​

February 4, 2026

Features​

Faster Dashboard Load Times During High Message Volumes​

We’ve improved dashboard performance during busy periods with high message volumes. Your stats now load faster, and you’ll avoid endless loaders or errors, even when syncing activity spikes.

Default Operator Now Set in Hive Explorer Filters​

We've improved the Hive Explorer filter experience by automatically setting a default operator when you select a property. This means fewer clicks and faster filtering.

Resizable Sidebar in Hive Explorer​

You can now drag the Hive Explorer sidebar to your preferred width. This setting is remembered in your browser, so it stays consistent on the same device and browser.

Excel Export Now Supports Large Datasets​

You can now export much larger Excel files from Hive Explorer, up to 1,000,000 rows. Previously, exports were limited to files under 10MB. If your export exceeds 1,000,000 rows, you’ll see a warning and can choose to proceed with a truncated export (first 1,000,000 rows only).

We’ve also added a new Downloads page. All Excel exports will now appear there, so you can easily track and download them anytime.

View Retrying and Scheduled-to-Retry Messages in the App​

You can now see which messages are currently retrying or scheduled to retry, giving you better visibility into SyncHive’s message processing. This view is read-only for now - retrying message management will be added in a future release.

Access it via Operate → Resync → Retries in the UI.

Note: Stuck and retrying messages are now grouped under the Resync page. The updated URL for stuck messages is: /resync?tab=stuck.

Clearer and More Helpful Error Messages Across SyncHive​

We’ve improved how SyncHive reports errors and warnings to make it easier to understand what went wrong and how to fix it. These updates replace vague or misleading messages with clearer explanations, specific error codes where relevant, and direct links to our documentation.

What’s improved:

  • Clearer error messages when a Connector sends a message in the wrong format
  • More specific error logging for invalid Hive IDs
  • Improved logging for correlation ID and external ID related errors and warnings
  • Updated event wording when a Connector or external system is unavailable, changing from “Platform unavailable” to “Connector unavailable” to better reflect the source of the issue

Bugs​

Fix Completed Outbound Messages Staying as Processing on the Dashboard​

We had an issue in the way we were updating our dashboard stats, resulting in a race condition that caused completed messages to go back to in process. This meant the dashboard incorrectly showed messages as in process when they were already complete.