Release Version 2.35.3

In this release, we have addressed the following issues to improve the usage and functionality of our product features. 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 Missing TOASTed Data for PostgreSQL Source

  • Fixed an issue affecting all variants of PostgreSQL Source, where TOASTed records were lost during batch processing if Hevo’s internal data processing system encountered downtime or failure. The issue occurred when Hevo attempted to retrieve data from PostgreSQL using a batch query, but could not process it because the system was unavailable. Since there was no fallback mechanism, any unprocessed data was lost.

    With this fix, if the internal system is down during such scenarios, the retrieved record will now be temporarily stored in Hevo’s temporary memory cache. When the system is back online, the data from the cache is processed, ensuring no data is lost. To enable this fix for your existing or new Pipelines, contact Hevo Support.

• Handling Token Refresh Issue in Pinterest Ads

  • Fixed an issue where, in some cases, Pinterest Ads Pipelines failed to refresh tokens automatically and needed a manual account reauthorization. This issue occurred because Hevo did not call the refresh token API when the access token expired. As a result, Hevo could not generate a new access token using the existing refresh token, leading to authentication errors.

    With this fix, Hevo now triggers the refresh token API before the access token expires. This enables automatic generation of new access tokens prior to expiration.