> For the complete documentation index, see [llms.txt](https://docs.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.collibra.com/data-quality-self-hosted/release-notes/data-quality-observability-self-hosted-release-archive/release-2026-01.md). # Release 2026.01 * [New and improved](#new-and-improved) * [Fixes](#fixes) ## Release Information * Release date of Data Quality & Observability (self-hosted) 2026.01: February 3, 2026 * Release notes publication date: January 21, 2026 ## New and improved ### Platform {% hint style="danger" %} In the upcoming Data Quality & Observability (self-hosted) version 2026.02, Spark 4 is required. Depending on your installation type, additional action may be required. * **Kubernetes installations**: The upgrade to 2026.02 is seamless and managed automatically within the application container. * **Spark Standalone installations**: You must manually upgrade your underlying Spark environment to Spark 4 before upgrading to version 2026.02. This is a mandatory prerequisite. To learn how to upgrade Spark, go to [Upgrade Spark](/data-quality-self-hosted/installation/agent/upgrade-spark.md). {% endhint %} * You can now configure email alerts using [OAuth 2.0 via Microsoft's Graph API](/data-quality-self-hosted/admin-configuration/admin-console/alerts/alert-configuration/configure-oauth.md) with a service-to-service client credentials flow. This modern configuration offers a secure alternative to classic SMTP authentication. To set up email alerts, register an application in Azure and enter its Client ID, Secret, and Tenant ID. * The Kubernetes Java client has been upgraded from version 21.0.2 to 25.0.0. This upgrade ensures compatibility with Kubernetes versions up to 1.34. * You can now configure email alerts using OAuth 2.0 via Microsoft's Graph API with a service-to-service client credentials flow. This modern configuration offers a secure alternative to classic SMTP authentication. To set up email alerts, register an application in Azure and enter its Client ID, Secret, and Tenant ID. * You can now require the Dimension setting for rules by enabling the "MANDATORY\_RULE\_DIMENSION" [configuration flag](/data-quality-self-hosted/admin-configuration/admin-console/configuration-settings/application-configuration-settings.md). When enabled, the Dimension field becomes mandatory for all rule types, ensuring rules cannot be saved without selecting a Dimension. * You can now [copy "Environment Details"](/data-quality-self-hosted/core-concepts/overview-data-quality-observability-self-hosted-core-concepts.md) directly to your clipboard from the "Application Info" button. This simplifies sharing environment information for Collibra Support. * When using the global search bar, you are now notified if your search yields no results. * We have updated the "terms" link on our sign in page. ### Jobs * You now see a more user-friendly and informative error message when manually triggering a DQ job on an S3 connection with expired or missing credentials. This helps you quickly identify and resolve the issue. * When you configure shapes for a Pushdown job without a link ID specified and enable "Archive breaks," break records are now archived in the source. Additionally, a new results column shows the source record in JSON format. ### Rules * Access to the Rule Result Preview feature is now restricted. Users must have the ROLE\_DATA\_PREVIEW security role to [view preview data](/data-quality-self-hosted/core-concepts/dq-rules/rule-builder/working-with-the-rule-workbench/create-a-data-quality-rule.md). * When you delete a rule, it is removed from all jobs run after the deletion date, and their scores are automatically recalculated. Jobs run before the deletion date remain unchanged, and the deleted rule's impact on the score is retained. ### Alerts * All dataset metatags are now available for use in [webhook](/data-quality-self-hosted/admin-configuration/admin-console/alerts/alert-webhook-configuration/add-webhooks.md) custom payloads. When a webhook is triggered, metatags are correctly passed in the JSON using placeholders such as "%%metatag\_1%%." Additionally, the business unit is now exposed as "%%business\_unit%%." ### Collibra Platform integration * You can now retrieve Snowflake table metadata through the API for the Explorer UI and auto-map. Auto-map automatically populates the dgc\_dq\_mapping table with table columns, simplifying integration. ### Admin * You can now configure how frequently Collibra Platform checks a connection's status when it's used in Explorer, using the new `explorer.dao.pool.connectionCleanerIntervalMSecs` configuration parameter. The default remains 60,000 milliseconds (60 seconds). ## Fixes ### Platform * You now see an informative landing page prompting you to set the license name if it wasn't configured during installation. After setting the license name and key, the page disappears. Previously, this process failed with a "403 Unauthorized" error, which has been resolved. * You can now fully disable Pendo scripts alongside other application properties, providing greater control over application configurations. ### Jobs * Downloaded break records now handle quoted data correctly, ensuring data with quotes is no longer split across multiple columns. Column headers with commas remain intact in the exported CSV. Additionally, dates in the "Preview Breaks" download now match the format shown in the UI, ensuring consistency when opened in Excel. * When you create an SAP HANA connection and run a job with a string field starting with "+" or "-", the job now runs and profiles the column as a string instead of showing an error. * The time window now displays correctly for IST and other half-hour offset time zones. Jobs no longer run during restricted periods, ensuring accurate scheduling. * You can now update the date range to a future date for an outlier without errors. This ensures smooth updates and allows breaks to be set until the specified end date. * Job estimates now validate tables for Snowflake data sources without errors. This ensures smoother operation and accurate validation during job execution. * The "Previous" and "Next" buttons are now hidden in the Explorer tree when the schema contains fewer than 25 tables. Previously, these buttons appeared as disabled. ### Findings * An issue that caused a user-passed adaptive rule violation to reset incorrectly when another adaptive rule was retrained or suppressed during a data job run has been fixed. Adaptive rule violations now remain unchanged during these operations. ### Rules * Rules now work with "REGEXP" in the same way as "RLIKE," including scenarios with parentheses. This ensures consistent behavior across both operators. * When you hover over "App Frequent Runs" in the dataset selection screen of the Alert or Rule Builder, the double line no longer appears. ### Connections * Filtering by schema or database name now correctly shows the associated schema and tables when you expand a relevant connection. The "Search Catalog" API returns valid results for existing schemas. Clearing the filter and expanding the connection now behaves consistently with filtered behavior. ### Collibra Platform integration * The UI now correctly shows "0/0/0" when the values for fully mapped, partially mapped, and total tables are zero. Previously, incorrect values could appear because default values were not set to 0. If any of these values are null or undefined, the UI will continue to show "N/A." ### APIs * The "v3/alerts" API now prevents null or empty values for the alertTriggerType and alert\_types parameters. This ensures more reliable API behavior and data validation.