Version 26.9.0

Date: 20th September 2026

• Global Storage (S3) Support for Redshift Serverless (Pushdown Engine) (ACR-2585) ADOC now supports persisting data quality policy results to Global Storage (S3) when running Redshift Serverless policies in Pushdown engine mode. Previously, this persistence was only available on the Spark engine, forcing customers to choose between Pushdown engine performance and S3 result storage. Good and bad row records are now accessible both through the Data Violations view in the ADOC UI and directly from your S3 bucket. For more information, see Configuring Redshift Spectrum for External Tables.
• Consistent Reliability Scores Across ADOC (ACR-2565) Reliability scores are now computed using the same formula and displayed consistently everywhere they appear — Discover Assets, Asset Overview, the Policies tab, Reliability Explorer, and Data Products (Marketplace and Manage Overview) — so the same asset shows the same score on every page. Scores reflect each rule's most recent execution result, aggregated according to the scoring methodology selected under Settings > Score aggregation methodology (Policy Based Simple Averaging, Rule Based Simple Averaging, or Rule Based Row Weighted Averaging). The score delta shown alongside each score reflects the change from the previous execution, and is no longer scoped to a fixed time window. For more information, see Score Aggregation Methodology.
• Absolute Change and Percentage Change Operators for Data Equality Reconciliation (ACR-2538) Data Equality reconciliation rules now support two new operators — Absolute Change and Percentage Change — that match source and target values within a defined tolerance instead of requiring an exact match. Absolute Change accepts a fixed amount of deviation from the source value; Percentage Change accepts a percentage of the source value; both support symmetric, one-sided, or asymmetric tolerance using independent Lower Bound and Upper Bound settings. For more information, see Reconciliation Policy.
• Crawler No Longer Archives Policies When S3 Assets Are Temporarily Unavailable (ACR-2533) The S3 crawler no longer deletes an asset when its underlying file or object is missing during a crawl — for example, due to a delayed upload or a brief storage interruption. The asset is now retained in its last-known state, so policies attached to it stay active and continue running on their configured schedule without requiring manual intervention. For more information, see Amazon S3.
• Configurable Delay for Pipeline Automations (ACR-2810) Pipeline automations for Profiling, Data Quality, and Reconciliation can now be configured with a delay, in minutes, before they run after their trigger (Pipeline, Job, or Span) completes. This helps stagger automation execution across a shared Data Plane cluster, reducing resource contention when multiple automations are triggered at the same time. For more information, see Pipeline Run Details.

• AWS Step Functions Pipeline Integration: ADOC now supports AWS Step Functions as a pipeline source, giving you visibility into Step Function executions alongside your other orchestrators. States within a Step Function appear as job nodes on the pipeline canvas, with nested visualization for Map and Parallel states. When one Step Function triggers another, you can link the two executions into a single connected pipeline view in ADOC by passing parent run context between them — the same pattern used for Airflow-to-Spark and Airflow-to-Dbt lineage. This integration supports Standard Step Functions only; Express Step Functions are not supported, and results reflect a completed execution rather than a live, in-progress view. For more information, see AWS Step Functions.
• Resource-Based Access Management (RBAM) for Pipelines: Pipeline access can now be scoped by domain, matching the access model already available for assets and reports. Admins can group pipelines into Pipeline Resource Groups — by explicit selection, by data source, or by a regex pattern matched against the pipeline's unique ID — and grant view or modify access to specific teams via a Domain Role's new Pipeline Management permissions. New pipelines, whether pulled in or pushed via OpenLineage, automatically join any resource group whose pattern matches, with no manual tagging required. At rollout, every tenant retains a default resource group covering all pipelines, so existing access is unaffected until an admin deliberately narrows it. For more information, see Roles and Permissions.