Release Version 2.36.2

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

• Fixes and Improvements

Fixes and Improvements

Sources

• Handling Data Ingestion Issues in Salesforce and Salesforce Bulk API V2

  • 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 Missing Issue in HubSpot

  • 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 False Error Message Issue in ElasticSearch

  • 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 Count Issue in Pipeline Objects List

  • 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 Skip Issue for Full Load Objects in NetSuite ERP

  • 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.