# March 2026 Release Note

These are the Treasure Data features and improvements released in March, 2026.

## Treasure Workflow

### Snowflake Workflow Operator

- The Snowflake Workflow Operator (`snowflake>`) lets Treasure Workflow execute SQL directly on customers' Snowflake warehouses for ETL, preprocessing (such as deduplication and ID unification), and other data preparation steps as part of a workflow.
- Designed for data engineers building composable CDP architectures, this non-blocking operator uses Snowflake's SQL API with support for retry, cancel, timeout, and `snowflake.last_results`, so long-running Snowflake queries are managed reliably without tying up workflow agents.
- Learn more by visiting the [Snowflake Workflow Operator](/products/customer-data-platform/data-workbench/workflows/operators/snowflake) page.


### Databricks Workflow Operator

- The Databricks Workflow Operator is a new Treasure Workflow operator that lets you submit and manage SQL and ETL processing directly on your Databricks environment using Databricks REST APIs.
- Designed for data engineers using Treasure Data CDP with Databricks and Live Connect, it enables preprocessing, deduplication, and ID unification to run on Databricks compute while Treasure Workflow orchestrates the full data pipeline.
- Learn more by visiting the [Databricks Workflow Operator](/products/customer-data-platform/data-workbench/workflows/operators/databricks) page.


### Upcoming Change: Schedule Resume Dialog Default

- In an upcoming update, the Resume Schedule dialog in Treasure Workflow will default to the "Running the next session" option. Once this change takes effect, re-enabled schedules will resume from the next scheduled run rather than automatically triggering catch-up or backfill runs.
- This change is intended to help reduce unexpected historical runs and unintended workloads when resuming disabled schedules.
- Learn more by visiting the [Resuming a Paused Workflow](/products/customer-data-platform/data-workbench/workflows/resuming-a-paused-workflow) page.


## Integration Hub

### New Connector: Streaming Egress Connector - Advanced Webhook

- The Advanced Webhook streaming egress connector is a new generic REST connector for RT2.0 that supports dynamic headers and body values, including HMAC-SHA256 signing with runtime expressions such as `${unix_timestamp()}`, `${http_method}`, and `${relative_path}`.
- This feature helps technical users like marketing engineers and data engineers securely integrate modern martech, adtech, fintech, SaaS, and security APIs (including Selligent's `triggerbyjson` endpoint) in real time without building or maintaining custom middleware for dynamic header signing.
- Learn more by visiting the [Secure Signed Webhook Streaming Export Integration](/int/ss-webhook-streaming-export-integration) page.


### Oracle Eloqua Export Connector: Unified Contact Destination and Folder Support

- The Oracle Eloqua Export connector now merges the legacy "Contact Shared List" destination into the main "Contact" destination and adds in-connector folder creation and selection to better match Eloqua's native data model and asset organization.
- Designed for B2B marketers and marketing operations teams using Eloqua for campaign execution, this update simplifies destination choice, reduces confusion from legacy behaviors, and helps keep exported Eloqua assets organized in the right folders from the start.
- Learn more by visiting the [Oracle Eloqua Export Integration](/int/oracle-eloqua-export-integration-1) page.


### Verizon Media (Yahoo! Ads) Connector: OAuth 2.0 Support

- This update upgrades the Verizon Media (Yahoo! Ads) export connector to use OAuth 2.0 for authenticating with Yahoo's DataX API in place of the deprecated OAuth 1.0 method.
- Advertisers and marketing teams using the Verizon Media connector can keep their existing export jobs running with improved security, without needing to change any job configurations or reconfigure authentication.
- Learn more by visiting the [Yahoo! Ads Export Integration](/int/yahoo-export-integration) page.


### Updated Microsoft JDBC Driver for SQL Server Input

- The Microsoft SQL Server Input connector now uses the latest compatible Microsoft JDBC driver, giving you access to the newest SQL Server features and security updates while preserving broad version support.
- This update benefits any customer importing data from Microsoft SQL Server into Treasure Data by improving security and compatibility without requiring changes to their existing import jobs.
- Learn more by visiting the [Microsoft SQL Server Import Integration](/int/microsoft-sql-server-import-integration) page.