Release Version 2.37
On This 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.
This release note also includes the fixes provided in all the minor releases since 2.36.
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
Sources
-
Support for Cursor-Based Pagination in Recharge (Added in Release 2.36.3)
-
Added support for cursor-based pagination in Pipelines created with Recharge Source. 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 Data Ingestion Issue in Salesforce Bulk API V2 (Fixed in Release 2.36.1)
- Fixed an issue where data from certain Full Load objects, such as
EntityDefinition, was being ingested in each Pipeline run instead of once every seven days. This behavior led to excessive consumption of Events. With this fix, Hevo now ensures that data from all Full Load objects is ingested every seven days. This fix applies to new and existing Pipelines.
- Fixed an issue where data from certain Full Load objects, such as
-
Handling Data Ingestion Issues in Salesforce and Salesforce Bulk API V2 (Fixed in Release 2.36.2)
-
Addressed the following issues in the task that Hevo automatically runs every 20 days to ingest historical data from all Salesforce objects containing calculated or derived fields:
-
Incorrect Data Ingestion: The task fetched historical data from objects that were skipped for ingestion from the Pipeline, leading to excessive Event consumption.
With this fix, Hevo now ingests historical data only for objects included in the Pipeline. The fix applies to all new and existing Pipelines created for Salesforce and Salesforce Bulk API V2.
-
Data Mismatch: Hevo ran the task in each of your Pipelines for all objects containing calculated or derived fields. However, it did not record the correct Pipeline ID or repeatedly fetched data from the same Pipeline, leading to mismatches between the Source and Destination data.
With this fix, Hevo now fetches the historical data correctly for all objects with calculated or derived fields. The fix applies to all new and existing Pipelines created for Salesforce Bulk API V2.
-
-
-
Handling Data Mismatch Issue for Item Types in NetSuite ERP (Fixed in Release 2.36.1)
-
Fixed an issue where updates to inventory data were not captured for the following real-time inventory item types, leading to mismatches between the Source and Destination data:
-
Inventory Item
-
Assembly Item
-
Lot Numbered Inventory Item
-
Serialized Inventory Item
This issue occurred because NetSuite does not update the lastModifiedDate field when a transaction affecting inventory takes place for these item types. As a result, Hevo could not detect changes based solely on this field, causing data discrepancies. With this fix, Hevo now uses the lastQuantityAvailableChange and lastModifiedDate fields to identify inventory-related updates. This ensures that inventory changes are captured even if no updates are made to the item type itself. If you notice a data mismatch in any of your existing Pipelines, contact Hevo Support to enable the fix for that Pipeline.
-
-
-
Handling Data Mismatch Issue in Twilio
-
Fixed an issue where the API call to fetch the Usage Records object for a specific date returned incorrect data. This issue occurred because the API call returned the sum of the field values for the selected date and the following day. As a result, the records in the Destination contained inflated values.
With this fix, the API now correctly retrieves only the data for the specified date.
To enable the fix for your existing and new Pipelines, contact Hevo Support. If you observe a data mismatch for the Usage Records object in your existing Pipelines, you must enable the fix and then restart the historical load for the object.
-
-
Handling Data Missing Issue in HubSpot (Fixed in Release 2.36.2)
-
Fixed an issue where data ingestion errors from HubSpot were not displayed or retried, resulting in missing fields in the Destination. This occurred because the data refresher task, which fetches deleted Events every 24 hours, was skipped if a previous run had occurred within the last 24 hours, even if the earlier run had failed. As a result, the failed task was incorrectly marked as successful, and no error was reported, causing unnoticed data loss.
With this fix, Hevo now verifies whether the previous sync failed and ensures that the next run is executed accordingly. This allows ingestion errors to be detected and prevents data loss. To enable this fix for your existing or new Pipelines, contact Hevo Support. For existing Pipelines, if you observe missing data in your Destination tables, you must enable the fix and then restart the historical load for that Source object.
-
-
Handling Duplicate Pipeline Creation Issue (Fixed in Release 2.36.3)
-
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 False Error Message Issue in ElasticSearch (Fixed in Release 2.36.2)
-
Fixed an issue where the Hevo user interface (UI) incorrectly displayed an error even though all active objects were configured correctly and ingesting data successfully. This issue occurred because Hevo’s error validation logic did not exclude tasks with the following statuses:
-
SKIPPED
-
NOT INCLUDED
-
PAUSED
-
FINISHED
-
HISTORICAL LOAD FINISHED
As a result, Hevo displayed misleading errors for inactive or already resolved objects.
With this fix, Hevo now shows this error message only for active tasks that impact data ingestion, thus preventing inaccurate error alarms for resolved or skipped objects. The fix applies to all new and existing Pipelines.
-
-
-
Handling Incorrect Billing Issue in File Storage Sources (Fixed in Release 2.36.3)
-
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.
-
-
Handling Incorrect Count Issue in Pipeline Objects List (Fixed in Release 2.36.2)
-
Fixed an issue in the Hevo user interface (UI) where the total count of Pipeline objects was displayed incorrectly when filters were applied. Specifically, when filtering by a query mode, such as Full Load, the count shown was higher than the count shown under All modes. This issue occurred because Hevo was counting each object multiple times, once for historical and incremental, instead of counting unique objects. As a result, the object counts in filtered views were inflated.
With this fix, Hevo now counts only unique objects, ensuring that the counts are accurate and consistent across all filter selections. Contact Hevo Support to enable this fix.
-
-
Handling Ingestion Lag Issues in Snapchat Ads (Fixed in Release 2.36.1)
-
Fixed an issue where data ingestion for Snapchat Ads was delayed due to incorrect time zone handling during the data fetching process. This issue occurred because Hevo miscalculated the data range needed to retrieve data. Specifically, the start date used for fetching data was inadvertently set earlier when converting from UTC to the Source’s local time zone. As a result, Hevo did not retrieve data for recent dates, even though the Snapchat Ads API had data available for them.
With this fix, Hevo has corrected the logic for calculating the date range, ensuring that data is fetched accurately for the intended days, regardless of time zone differences. The Pipeline now consistently ingests the most recent data available, eliminating the delay.
-
-
Handling Ingestion Skip Issue for Full Load Objects in NetSuite ERP (Fixed in Release 2.36.2)
-
Fixed an issue where Full Load objects were not ingested as expected during scheduled daily runs, causing delays in data ingestion. This issue occurred because Hevo enforced a strict 24-hour interval between the completion time of the previous Full Load ingestion and the start time of the next run. If the interval was slightly less, the ingestion was skipped. For example, if an ingestion was scheduled at 12:00 AM and completed by 12:03 AM, the next day’s ingestion, also scheduled at 12:00 AM, would be skipped, as it was triggered before the 24-hour interval had elapsed.
With this fix, Hevo now applies a 23-hour threshold between runs, ensuring that Full Load ingestions happen on schedule and that ingestion delays are avoided. The fix applies to new and existing Pipelines.
-
-
Handling Missing Data Issue in Jira Cloud
-
Fixed an issue where data for the board object was missing in the Destination. Earlier, if any of its child objects, such as projects, sprints, and issues, failed during ingestion, Hevo would stop ingesting data for the entire board. This meant that even error-free data from other child objects was skipped, resulting in missing records in your Destination.
With this fix, Hevo now handles failures at the child object level. If a specific child object fails, Hevo logs the error but continues to ingest the rest of the board and its remaining child objects. This ensures that partial failures do not impact the overall data ingestion. This fix applies to all new and existing Pipelines. For existing Pipelines, if you observe missing data in your Destination, restart the board object.
-
User Experience
-
Handling Display Issue for Event Types in the Schema Mapper User Interface (Fixed in Release 2.36.3)
-
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.
-
Documentation Updates
The following pages have been created, enhanced, or removed in Release 2.37: