Edge Release Notes - February 2026
On This 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
New and Changed Features
Pipelines
5 Minute Sync Frequency Option for All Users
EnhancedIntroduced the 5 minute sync frequency option for all users during Pipeline creation and editing. Previously, this option was enabled only on request through Support. You can now select it directly without any additional intervention. This helps reduce data latency and improve data availability in your Destination.
Support for External Orchestration in Pipelines
NewHevo now supports using external workflow managers, such as Apache Airflow, to trigger and manage your Pipelines. Previously, the Pipelines were limited to Hevo’s native scheduling, which could make it difficult to keep data replication in sync with external system events. Using the Hevo Airflow Provider, you can integrate Pipelines directly into your end-to-end DAGs to coordinate upstream triggers, such as Cloud Storage file uploads, and downstream tasks, such as dbt transformations. With this enhancement, you can shift from fixed, interval-based polling to a flexible, demand-driven model managed entirely by the external orchestrator.
Support for Precise Start Times in Pipeline Schedules
NewHevo now supports setting a specific start time in hh:mm (UTC) for Pipelines configured with a 24-hour sync frequency. Earlier, the Pipeline start time depended on the completion time of the previous run, which could result in unpredictable data availability at the Destination. With this enhancement, your 24-hour Pipeline syncs data at a fixed time (UTC) each day. This allows you to align the Pipeline runs with downstream processes, such as Source maintenance windows. Contact Hevo Support to enable this feature for your new and existing Edge Pipelines.
Sources
Support for BambooHR as a Source
NewIntroduced BambooHR as a Source for creating Pipelines in Hevo. BambooHR is a human resources information system (HRIS) that helps organizations manage employee data, time off, training, and performance-related information. This integration enables you to replicate HR data from your BambooHR account into your Destination for analytics and reporting.
BambooHR →Support for XMIN Pipeline Mode in PostgreSQL
NewIntroduced support for XMIN Pipeline mode in all variants of PostgreSQL Source. You can now create Pipelines using this mode to capture incremental changes by tracking the XMIN column. This allows Hevo to track newly inserted and updated rows without accessing the Write-Ahead Logs (WAL). You can also enable the Capture Deletes option while configuring the Pipeline to track deleted records, as XMIN does not capture deletes by default.
XMIN →
User Experience
Schema Mismatch Notifications for SQL Server Change Data Capture
NewHevo now alerts you through the user interface (UI) if it detects schema mismatches between the Source table and its associated CDC change table. This warning appears when columns are added or modified in the Source table after CDC is enabled. Previously, the Pipeline continued syncing data without notifying you of any schema changes, so you had to manually identify them and re-enable CDC on the affected tables to keep data consistent. With this enhancement, Hevo prompts you to re-enable CDC for the affected tables so that future data is replicated using the updated schema. Data ingestion for the table continues even while the warning is displayed, using the currently configured CDC setup. This feature is available for all Edge Pipelines configured with CDC mode.
Support for Hevo Stored Procedures in SQL Server Source
NewHevo now automatically enables Change Data Capture (CDC) or Change Tracking (CT) on SQL Server tables during ingestion, provided the required stored procedures are installed in the database. Previously, tables without CT or CDC enabled were marked as inaccessible in the Pipeline, and data was not ingested from those tables. With this enhancement, if Hevo detects that CT or CDC is not enabled for a table, it automatically runs the required stored procedures and enables a supported ingestion mode. This ensures that new tables remain accessible without requiring manual configuration. This feature is currently in BETA and is available for new and existing Pipelines that use a SQL Server database where the required stored procedures are installed. To enable it for your team, contact Hevo Support.
Hevo Stored Procedures for Change Tracking and Change Data Capture →Fixes and Improvements
Performance
Improved Performance of Pipelines with a Large Number of Objects
Improved the performance of Pipelines containing more than 10,000 objects by significantly reducing load times for the Pipeline review page and speeding up job initialization. Previously, Hevo fetched details for each object individually from the metastore. As a result, the Pipeline review page loaded slowly during the create and edit flows. Additionally, newly created Pipelines got stuck in the Initializing state for a long time before moving to Enabled. With this improvement, Hevo now fetches object details from the metastore in batches instead of individually. As a result, the Pipeline review page loads faster, and Pipelines move to the Enabled state more quickly. This improvement applies to all new and existing Pipelines.
Sources
Handling Incremental Failure Issue in PostgreSQL Sources
Fixed an issue across all variants of the PostgreSQL Source where incremental ingestion failed while processing delete events. This issue occurred for objects containing GEOMETRY column defined as NOT NULL. When a record is deleted in the Source table, Hevo assigns NULL values to all non-primary key columns in the deleted record. For tables with GEOMETRY columns defined as NOT NULL, this behavior caused schema validation errors, resulting in incremental ingestion failures. With this fix, Hevo ensures delete events are processed without violating NOT NULL constraints, ensuring incremental ingestion does not fail.