Release Version 2.45.1

Last updated on Feb 16, 2026

This is a minor release and will be integrated into the next major release. At that time, this release note will be merged into the next main release note.

The content on this site may have changed or moved since you last viewed it. As a result, some of your bookmarks may become obsolete. Therefore, we recommend accessing the latest content via the Hevo Docs website.

In this Release


New and Changed Features

User Experience

  • Hevo SaaS Offering on Snowflake Marketplace

    • Introduced the Hevo SaaS offering via Snowflake Marketplace, enabling customers to subscribe with customized pricing, contract terms, or payment schedules. Customers can contact Hevo Support to request a private offer. Existing Snowflake Marketplace Capacity Drawdown (MCD) credits can be used toward the purchase.

Fixes and Improvements

Sources

  • Handling Events Loading Issue in LinkedIn Ads

    • Fixed an issue where Events were not loaded for Ad Analytics object in some Pipelines. This issue was introduced in Release 2.43.3, when Hevo added support for the audience_penetration and average_dwell_time fields. While querying these fields, Hevo did not include dateRange, which is required to derive the date value. The date and campaign_id fields together form the composite primary key for the object. Since the query excluded dateRange, Hevo could not derive the date value, resulting in NULL. As date cannot be NULL, the Events failed validation and were not loaded.

      With this fix, Hevo now includes dateRange when querying for audience_penetration and average_dwell_time. This ensures that the date value is properly derived, the composite primary key is valid, and all Events are loaded as expected. This fix applies to all new and existing Pipelines. To ingest the missing data in existing Pipelines, restart the historical load for the Ad Analytics object.

  • Handling Pipeline Failures for Sharded Clusters in OpLog Mode in MongoDB

    • Fixed an issue where Pipelines could be created with sharded MongoDB clusters using OpLog mode, even though this configuration is not supported. This issue occurred because each shard in a sharded cluster maintains its own OpLog, making it difficult for Hevo to read and manage them. As a result, such Pipelines failed during ingestion.

      With this fix, Hevo no longer allows you to create Pipelines that use sharded clusters with OpLog mode. To create a Pipeline with a sharded cluster, use Change Stream mode instead.

Tell us what went wrong