Release Version 2.30

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.

This release note also includes the fixes provided in all the minor releases since 2.29.

To know the complete list of features available for early adoption before these are made generally available to all customers, read our Early Access page.

To know the list of features and integrations we are working on next, read our Upcoming Features page!

In this Release

• Fixes and Improvements
• Documentation Updates

---

Fixes and Improvements

Data Ingestion

• Handling of Incorrect Deferred Data Ingestion (Fixed in Release 2.29.3)

  • Fixed an issue where data ingestion was delayed in some cases if a poll was interrupted for any reason. This issue occurred because the system incorrectly scheduled the next ingestion for a longer duration than the intended deferment period when no Events were ingested during the interrupted poll. With this fix, Hevo now correctly applies the deferment period, ensuring timely data ingestion.

Sources

• Handling Data Ingestion Issue in PostgreSQL Source (Fixed in Release 2.29.1)

  • Fixed an issue in all variants of the PostgreSQL Source where, in some cases, Hevo repeatedly attempted to fetch data even when a polling job failed, leading to excessive queries and higher costs. Now, after five consecutive failures, Hevo marks the current polling job as failed. The next poll resumes fetching data as per the Pipeline schedule, ensuring seamless data ingestion.

• Handling Data Mismatch Issue in Shopify Source (Fixed in Release 2.29.1)

  • Fixed an issue where Hevo incorrectly set the id field as a primary key for the Product Image object after ingesting the Events. The id field values across all records were not unique, which caused one data record to be overwritten by another, resulting in incorrect data. With this fix, the primary key now consists of the product_id and id fields to identify each data record uniquely, ensuring that all data is correctly loaded into the Destination.

    The fix applies to Pipelines created with Shopify as a Source after Release 2.29.1. If you observe a data mismatch for the Product Image object in your existing Pipelines, you must create a new Pipeline.

• Handling Timeout issue on Source Files page for Azure Blob Storage Source (Fixed in Release 2.29.3)

  • Fixed an issue where users were unable to view the ingested files due to a timeout on the Source Files page. This issue occurred when the compressed files in the Source contained an invalid JSON file as the last file. Hevo marked this file as failed but was unable to skip it, causing repeated ingestion attempts and resulting in page timeout. With this fix, Hevo now skips the failed file, preventing repeated ingestion attempts.

Documentation Updates

The following pages have been created, enhanced, or removed in Release 2.30:

Destinations

• Snowflake

Sources

• Amazon Aurora MySQL

• Amazon Aurora PostgreSQL

• Amazon DynamoDB

• Amazon RDS MySQL

• Amazon RDS Oracle

• Amazon RDS PostgreSQL

• Amplitude Analytics

• Azure MySQL

• Azure PostgreSQL

• Azure SQL Server

• ClickUp

• Elasticsearch

• Facebook Ads

• Facebook Page Insights

• Freshsales

• Generic MongoDB

• GitLab

• Google Cloud MySQL

• Harvest

• Instagram Business

• Jira Cloud

• Missive

• PandaDoc

• Productboard

• Shopify Webhook

• Snapchat Ads

• Streak

• Stripe

• Trello

• Twilio

• Workable

Transform

• SQL Models

  • Working with SQL Models