Share

Release Version 2.44

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.

This release note also includes the fixes provided in all the minor releases since 2.43.

To know the complete list of features available for early adoption before these are made generally available to all customers, read our Early Access page.

In this Release

New and Changed Features

Destinations

  • Improved Support for Snowflake JDBC Driver

    • Upgraded the Snowflake JDBC driver from version 3.14.0 to version 3.27.1. The earlier version is no longer supported by Snowflake. This upgrade ensures continued compatibility and support and does not require any action from your side.

Sources

  • Support for Full Load Ingestion for Facebook Ads Objects (Added in Release 2.43.2)

    • Added support to ingest Ads, Ad Sets, and Ad Campaigns using Full Load mode instead of relying only on the updated_time field to fetch incremental changes for these objects. However, Facebook Ads does not reliably update this field, leading to stale or missing data and frequent data mismatch issues.

      With this enhancement, you can now enable Full Load ingestion for these objects, ensuring that Hevo replicates the complete dataset during each ingestion. This may result in an increased Event quota consumption. Read Facebook Ads for more information.

  • Support for Poll Strategy Configuration in NetSuite ERP (Added in Release 2.43.3)

    • Added support for setting the poll strategy for each NetSuite ERP object. You can now choose between the following poll strategies:

      • Basic Search: Replicates all available fields for the object.

      • Advanced Search: Allows you to select only the fields you want to replicate.

      This enhancement provides you with more control over how data is retrieved from NetSuite, helping to improve API performance, reduce payload size, and prevent search timeouts when working with large or complex objects.

Fixes and Improvements

Sources

  • Handling Connection Failures for SendGrid

    • Fixed an issue where Hevo failed to connect to SendGrid Sources configured only for non-marketing (transactional) data. Earlier, Hevo validated the marketing.read permission during connection, even when marketing data was not required. As a result, API keys created without Marketing Campaigns enabled could not be used, causing the connection to fail.

      With this fix, marketing permissions are optional, ensuring a successful connection even when marketing data is unavailable. Existing API keys without the marketing.read permission can be used to connect to Hevo. If you later need to ingest marketing data, create an API key with the required marketing permissions and modify the Source configuration of your existing Pipeline.

  • Handling Missing Records in MongoDB Change Streams

    • Fixed an issue where some updated records from MongoDB were not reflected in the Destination. This issue occurred because, in some cases, Hevo’s change stream processing logic could not correctly identify the document IDs to be extracted, resulting in some updated events to be skipped. With this fix, Hevo now applies the correct ID extraction logic based on the MongoDB version, ensuring that updates made at the Source are accurately captured and reflected in the Destination.

      This fix applies to all new and existing Pipelines. If you observe missing data for any object in an existing Pipeline, restart the historical load to ingest the missing data.

  • Handling Pipeline Stuck Issues in MySQL Sources (Fixed in Release 2.43.3)

    • Fixed an issue across all variants of MySQL Source where Pipelines could get stuck during subsequent runs after encountering errors while processing BinLog events.

      This issue occurred because, in some cases, if multiple consecutive BinLog events failed and a later event was processed successfully, the offset advanced based on the last processed event rather than the last successfully ingested one. As a result, Hevo miscalculated the offset. During the next sync, the Pipeline attempted to resume ingestion from an invalid BinLog position, resulting in the Pipeline getting stuck.

      With this fix, Hevo accurately tracks successfully ingested and failed BinLog events and subsequent syncs always resume from a valid BinLog position. This fix applies to all new and existing Pipelines created with any variant of MySQL Source after Release 2.17.

  • Handling Refresher Task Failure Issues in Snapchat Ads (Fixed in Release 2.43.2)

    • Fixed an issue where refresher tasks for Snapchat Ads failed on Daylight Saving Time (DST) transition days. This issue occurred because Hevo calculated the data window for each refresher run by adding a fixed 24-hour interval. On DST transition days, such as the fall-back day, the clock is set back by an hour, and the day becomes longer than 24 hours. In such cases, using a fixed 24-hour interval may result in an incorrect end timestamp, causing the refresher task to fail.

      With this fix, Hevo now calculates the data window based on the user’s time zone rather than a fixed time interval, ensuring that the date range is always computed correctly on DST transition days. To enable this fix for your new and existing Pipelines, contact Hevo Support.

  • Missing Ad Analytics Metrics in LinkedIn Ads (Fixed in Release 2.43.3)

    • Fixed an issue where the audience_penetration and average_dwell_time fields were not visible in the Schema Mapper and were not ingested for the Ad Analytics object in some Pipelines. This issue occurred because these fields, introduced in the Version 202503 API upgrade, were not included in the query used by Hevo to fetch data. As a result, although the data was available at the Source, it was not ingested.

      With this fix, Hevo now correctly queries these fields, ensuring these fields are ingested correctly going forward. This fix applies to all new and existing Pipelines. For existing Pipelines, values for these fields will appear as NULL for data ingested before Release 2.43.3. To ingest the missing data, restart the historical load for the Ad Analytics object.

User Experience

  • Handling Issue with Disabling Custom Full Load Frequency (Fixed in Release 2.43.2)

    • Fixed an issue where the Change Full Load Object Ingestion Schedule option remained enabled even after users attempted to disable it. This affected Pipelines created using the following Sources:

      • Amazon Ads

      • Facebook Ads

      • Jira Cloud

      • NetSuite SuiteAnalytics

      • Snapchat Ads

      • Zendesk

      With this fix, disabling the option now works correctly, ensuring all objects in the Pipeline follow the Pipeline ingestion schedule. This fix applies to all new and existing Pipelines.

Documentation Updates

The following pages have been created, enhanced, or removed in Release 2.44:

Sources

Last updated on Jan 12, 2026

Tell us what went wrong

Skip to the section