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

Pipelines

• Handling API Timeout Issue while Fetching Objects List for Facebook Ads Source

  • Fixed an issue in Pipelines where the Hevo UI sometimes took longer than expected to display the list of Source objects in the Pipeline Detailed View. This occurred because fetching the object list required an additional API call to retrieve the OAuth token ID for the Pipeline, which was routed through servers in the Asia region. For Pipelines in other regions, this additional latency caused the API to exceed its 30-second time limit and time out.

    With this fix, Hevo removes the unnecessary API call to the Asia server, reducing latency and ensuring the object list loads within the time limit.

    This fix applies to all new and existing Pipelines.

Sources

• Handling Inconsistent Data Refresher Tasks for Google Sheets

  • Fixed an issue where the refresher task for Google Sheets was triggered only if exactly 24 hours had passed since the last run. This caused scenarios where the refresher task ran inconsistently if the previous refresher task ended slightly under 24 hours, creating a gap between runs and resulting in missing data.

    With this fix, the refresh timing logic has been adjusted to account for minor differences in task completion time, ensuring that the refresher task runs consistently every day and eliminating gaps in data refresh. This fix applies to all new and existing Pipelines.

• Handling Unsupported Object Issue in Salesforce and Salesforce Bulk API V2

  • Fixed an issue where the unsupported Salesforce object ActivityMetric was visible in the UI and could be selected for ingestion. This issue occurred because Hevo did not validate whether the object was supported and queryable before adding it to the Pipeline schema. With this fix, ActivityMetric has been removed from the schema and is no longer selectable, preventing ingestion failures.