Changelog
HomeRequest DemoContact
Start typing to search…
Back to All

Changelog 6.0

September 3rd, 2025 by Sophy Ting

Validio 6.0 adds support for user-defined priority and improvements to how we show errors on resources in the system.

User-defined Priority

Updating a Priority of a source.

The priority score for incident groups is no longer automatically computed. Instead, you can now set the priority (None, Low, Medium, High, Critical) on your sources and validators during configuration. If you want to change the priority of a source or incident, you can update it from the list of sources or validators on their respective pages.

An Incident will inherit the priority of the source or validator where it is detected. Similar to ownership inheritance, the priority of the validator will override the source. You cannot change the priority of an incident.

We are looking into adding support for routing notifications based on user-defined priority for a future release of Validio.

Improved Resource Errors

Error badges and messages viewed in a Source Validator tab.

We redesigned the notification of errors within the UI to be more localized to the resource they affect. Instead of listing all errors on a global page, you will see errors directly on the affected resource. For example, we added polling errors directly on the sources and validators, segmentation limits on segmentations, and field errors on all affected resources. If there are errors on a validator, schema, filter, window, or segmentation, you will see a badge with the error count on the relevant tab on the Source's details page. For more information, see About Source Errors.

6.0.1

Validio 6.0.1 was released on 15 September 2025.

Fixed Issues

  • Fixed redirect after logging in with SSO (UI-5354)
  • Fixed validation when configuring a SQL Source for Snowflake (UI-5357)

6.0.0

Validio 6.0 was released on 10 September 2025.

Deprecations and Removals

  • Removed deprecated authHeader and webhookUrl from MSTeams and Slack channels (UI-5266)
  • Removed support for switching algorithm versions of Dynamic Thresholds. Dynamic Thresholds V2 is the new default and the only algorithm supported for new validators. For now, this will not affect existing validators using V1. (UI-5334)

Fixed Issues

  • Fixed filtering on Owner for data quality graph (UI-5291)
  • Fixed partial updates for some credentials and email (UI-5141)
  • Fixed an issue where all characters were sometimes not visible in input fields (UI-5250)
  • Fixed empty Activity when validator is deleted from a deleted source (UI-5261)

New Features and Updates

  • Added priority setting to sources and validators (UI-5288, UI-5324, UI-5292)
  • Added support for multiple SAML auth backends (UI-4305)
  • Added Incident group link to incident status update activities (UI-5298)
  • Added field errors and broken resources (UI-5154)
  • Added credential catalog refresh to Activity (UI-5282)
  • Changed freshness tumbling window closing time to clocktime (VR-4619)
  • Enable catalog by default for BI Tool credentials (UI-5253)
  • Increase max sensitivity to 8 for dynamic threshold configuration (UI-5320)
  • Increase pagination limit to 100 for Validator Segments list (UI-5322)
  • Allow users with Viewer role to preview threshold updates (UI-5245)
  • Allow SQL Server and Oracle credentials to be selected as dbt warehouses (UI-5257)
  • Exposed CatalogAsset query APIs (UI-4521)
  • Replaceed credential type selection with combobox for Oracle and SQL Server (UI-5209)
  • Updated incident colors and various UX improvements in the browser extension (UI-5311, UI-5256)