Validatar has a new release! From major updates to minor bug fixes, we’re constantly working to improve your Validatar experience so you can continue to build trust in your data. Learn about what’s new below.
Release Date
Validatar 2026.1.1 will be released to cloud environments on the evening of July 24, 2026.
What’s New!
AI Tools: Folder and Project Management
The Validatar AI agent and MCP server now support organizing your workspace directly through natural language.
Six new tools are available:
Create Folder: create a new test or job folder inside a project
Rename Folder: rename an existing folder
Move Folder: move a folder to a different parent location within a project
Delete Folder: delete an empty or specified folder
Create Project: create a new project with data sources, permissions, and custom fields
Update Project: modify the name, description, data sources, permissions, or custom field values on an existing project
All six actions are reversible from the Validatar AI chat history or from the revert_action MCP tool.
Schedules Report Dataset
A new built-in report dataset, Schedules, is available in the Reports section. It provides a comprehensive view of all schedulable tasks.
Fields include:
Schedule type
Project name
Schedule Recurrence (hourly, daily, weekly, monthly, etc.)
Start and end dates/times and time interval
Last/Next execution dates
Additional detail depending on the schedule type
The Schedules dataset supports the same filtering, sorting, export, and saved-report capabilities as other built-in datasets.
SMTP OAuth 2.0 Authentication
SMTP email delivery now supports OAuth 2.0 client credentials as an authentication method, in addition to the existing Windows Default Credentials and Basic Authentication options.
A new Authentication Method selector on the SMTP settings page lets administrators choose between Default Credentials, Basic Authentication, and OAuth.
When OAuth is selected, fields for Issuer URL, Scope, Client ID, and Client Secret are displayed.
This enables compatibility with modern mail providers (such as Microsoft Exchange) that are deprecating basic authentication.
Other Highlighted Enhancements
The database schema for storing built-in engine test results has been modified to allow higher concurrency without causing deadlocks. Refer to the Upgrade Notes section below for more information on this enhancement.
Data Agent deployments that use Column Aggregation or Row Count for dataset post-processing with the built-in engine now apply that processing before transmitting results to a Validatar instance, which potentially dramatically reduces the volume of data that is transferred.
Bug Fixes
Snowflake test comparison timeout: Fixed an issue with the Snowflake engine that occasionally caused a processing error when saving test results under high concurrency.
Databricks engine: Updated the Databricks engine to correct a script error caused by a breaking-change made by Databricks.
Data Agent date handling: Data agents no longer truncate milliseconds from date/time values pushed to Snowflake/Databricks engines.
Fixed security vulnerability: An embedded package used by data agents to compress data before transmitting to a Validatar instance was updated to a version that resolves a reported security vulnerability (https://nvd.nist.gov/vuln/detail/CVE-2026-48509).
Custom profile formulas: Custom profile formulas that reference database or schema metadata fields now evaluate correctly.
Task state management: The underlying task state management system in cloud instances was upgraded to support higher concurrency. The old system occasionally lost track of state under high concurrency.
Increased script size: Cloud instances now support multi-MB test dataset scripts.
Upgrade Notes
Duration of Data Migration
For environments that contain a large number of test result records, the initial migration of historical test results to the new structure could take a significant amount of time. The migration process occurs in three phases:
The database table structure is modified so that new test results can be stored, which should take at most a few minutes. This phase occurs when Validatar is first accessed after the new version is installed.
Historical test results are migrated to the new structure, which could take several hours depending on volume. Historical data is migrated in batches with a background task that starts with the most recent test results and then progressively moves backward in time until all historical test results have been migrated.
Once all historical test results have been migrated, the database structure is again modified to drop old unused columns and apply new indexes to increase performance with the new table structure.
Nine new database upgrade scripts are applied automatically on first startup to upgrade the database schema to version 2026.1.1.9.
SMTP settings: existing configurations using Default Credentials or Basic Authentication will be migrated automatically. No administrator action is required.