Release Version 2.37.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

• Fixes and Improvements

Fixes and Improvements

Sources

• Handling Data Ingestion Issues in HubSpot

  • Fixed an issue where data ingestion was delayed for objects with a large volume of data. This issue occurred because HubSpot sets a limit on the number of API requests allowed for an object within a time frame. If this limit was exceeded during a poll, Hevo would skip fetching data for that object until the next polling cycle, causing a delay in data ingestion.

    With this fix, when the API rate limit is exceeded for an object during a poll, Hevo now waits for 10 seconds and then retries fetching data from that object, up to 5 times. This ensures data from all objects is ingested with minimal delay. If all retries fail, Hevo attempts to fetch data in the next polling cycle. To enable the fix for your new and existing Pipelines, contact Hevo Support.

• Handling Data Mismatch Issue in QuickBooks Online

  • Fixed an issue where the timestamp fields for the Invoice object were incorrectly detected as LONG data type, resulting in incorrect values being populated in the Destination. This issue occurred because Hevo converted date fields such as due_date and txn_date, into Unix timestamps during ingestion. A Unix timestamp represents a date and time as the number of milliseconds since January 1, 1970. These large numeric values did not match the expected DATE format in the Destination, leading to data type mismatches.

    With this fix, Hevo now correctly parses date fields such as due_date and txn_date in the expected DATE format, ensuring accurate data mapping in the Destination. To enable the fix for your existing and new Pipelines, contact Hevo Support. If you observe a data mismatch for the Invoice object in your existing Pipelines, you must enable the fix and then restart the historical load for the object.