Release Version 2.36.3

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
• Fixes and Improvements

New and Changed Features

Sources

• Support for Cursor-Based Pagination in Recharge

  • Added support for cursor-based pagination in Recharge Pipelines. Previously, historical loads could fail when more than 5,000 records were fetched from an object, due to the Recharge API’s limit of 100 pages with page-based pagination. This limitation resulted in ingestion errors for larger datasets. With this enhancement, Hevo now uses cursor-based pagination by automatically following the next page link included in the Recharge API response. This enables Hevo to ingest data beyond the 100-page limit.

    This enhancement applies to all new Pipelines created with this Source. If you have an existing Pipeline and observe ingestion issues due to pagination limits, contact Hevo Support to upgrade your Pipeline.

Fixes and Improvements

Sources

• Handling Duplicate Pipeline Creation Issue

  • Fixed an issue where Pipelines created in quick succession from the same Source were sometimes assigned the same serial number, causing Hevo to consider them as duplicates. This caused inconsistencies in the UI as multiple Pipelines appeared with the same identifier.

    With this fix, Hevo ensures that each Pipeline within a team is assigned a unique serial number, even when created simultaneously.

• Handling Incorrect Billing Issue in File Storage Sources

  • Fixed an issue where Events from historical data were incorrectly marked as billable in file storage Sources such as Amazon S3, Azure Blob Storage, FTP/SFTP, GCS, Google Drive, and Google Sheets. Earlier, Hevo’s billing logic verified only whether a file was modified before the Pipeline creation date, without checking if the task belonged to a historical load. As a result, when historical load was restarted and the files were modified after the Pipeline creation, those Events were incorrectly counted in incremental ingestion and billed.

    With this fix, Hevo now correctly identifies tasks associated with historical loads, regardless of the file modification time. This ensures that only incremental Events are billed.

User Experience

• Handling Display Issue for Event Types in the Schema Mapper User Interface

  • Fixed an issue in the Schema Mapper user interface (UI) where some Source Event Types were either missing or displayed multiple times. This issue occurred because the underlying SQL query used by Hevo to paginate the list of Event Types could not determine the correct sort order. The sorting was done based only on the status of the Event Type, such as MAPPED, UNMAPPED, or SKIPPED, leading to inconsistent sorting.

    To fix this issue, the sorting logic is enhanced. The SQL query now includes the unique ID assigned to each Event Type by the Schema Mapper, ensuring a consistent and accurate order. This fix applies to both new and existing Pipelines.