Release Version 2.27.2

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

• Fixes and Improvements

Fixes and Improvements

Data Loading

• Handling Incorrect Data Spike Alerts Due to Time Zone Differences

  • Fixed an issue where Data Spike Alerts were generated using UTC time zone, which caused data from two days to overlap for users in different time zones. As a result, users received incorrect alerts with higher than actual Event counts. With this fix, Data Spike Alerts are now aligned with users’ local time zones, ensuring accurate Event counts and preventing incorrect alerts.

Sources

• Handling of Data Ingestion Issues in Salesforce Bulk API V2 Source

  • Fixed the following issues in the Salesforce Bulk API V2 integration:

    • High data ingestion: Hevo repeatedly re-ingested the same data in consecutive polls after a poll failure, resulting in high data ingestion and Events count. The issue occurred because the locator, which tracks the last ingested page of records, was set to null after a poll failure. This caused Hevo to re-ingest previously fetched records. With this fix, Hevo now retrieves the locator that is stored in offset, ensuring accurate data ingestion.

    • Data ingestion delay: The data ingestion task was incorrectly marked as completed while the polling job was still in progress. This led to a delay in data ingestion as the next ingestion task was scheduled based on the Pipeline frequency. With this fix, if the polling job is still in progress, the ingestion task is deferred and retried every 5 minutes, ensuring timely data ingestion.