Release Version 2.24.1

Last updated on Jun 19, 2024

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.

In this release, we have addressed the following issues to improve the usage and functionality of our product features. To know the list of features and integrations we are working on next, read our Upcoming Features page!

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


  • Support for Availability Group in SQL Server Source

    • Enhanced the SQL Server integration to support creating Pipelines with an SQL Server instance, which has the Always On availability group (AG) functionality enabled. This enhancement allows you to configure one of the secondary databases in the AG as a Source in your Hevo Pipeline.

      To avail this feature for your team, you need to contact Hevo Support. When the Support team enables the feature for you, you must select the Set Application Intent Read Only option while configuring your Hevo Pipeline.

      Set Application Intent Read Only

      Enabling this option allows Hevo to connect seamlessly to your secondary database and ingest data from it instead of your primary database instance.

Fixes and Improvements


  • Faster Ingestion from BigCommerce Source

    • Improved the data ingestion process for the Orders object in BigCommerce by introducing pagination to avoid delays while reading data from it. The enhanced process comprises:

      • Increased Page Size: Hevo now sets the page size parameter to ingest up to 250 records in each Pipeline run. If more than 250 records are received, Hevo paginates the response and continues reading data till it gets an empty page. Earlier, Hevo ingested only 50 records per run, which is the default page size for the Orders API in BigCommerce.

      • Offset Management: Hevo now maintains an offset based on the updated_at field of the last received record. The offset allows Hevo to determine the starting point for subsequent pages, as the Orders API does not provide a next-page offset.

      This fix applies to new and existing Pipelines.

  • Handling of Records Missed During Historical Load for Stripe Source

    • Fixed an issue in Stripe where the loading task failed to ingest data for the last day of the specified historical load duration, resulting in data mismatch between the Source and the Destination. Hevo now correctly ingests the complete historical data for the defined period.
  • Resolving Data Ingestion Issue for BigQuery Source

    • Fixed an issue in the BigQuery integration where adding new columns with default NULL values to a Source table included in the Pipeline led to an increase in the data ingested. This issue occurred because while mapping the new columns to the Destination table, Hevo re-ingested all the data from the Source table. Now, Hevo maps the newly added Source column to the Destination table only when it identifies a change in the data for that column, thus reducing the cost incurred, the resources consumed, and the time taken for data ingestion. The earlier behavior of re-ingesting all data from the Source object when newly added columns have non-null default values remains unchanged.

      To make this fix available for your BigQuery Pipeline, you need to contact Hevo Support.

User Experience

  • Simultaneous Selection of Multiple Columns for Skipped Objects

    • Fixed an issue in the user interface that prevented users from selecting multiple columns at once from the drop-down for the Unique Incrementing Append-Only (UIAO) query mode. This issue occurred when the UIAO query mode was selected for objects included in the Pipeline after its creation.

Tell us what went wrong