Running a validation
Once a validation has been configured, you can execute it either on demand or according to a recurring schedule. This topic describes how to start a validation run, how scheduled executions are handled, how to pause or resume a validation's schedule, and how to monitor validation progress.
A validation supports two execution modes:
Recurring run: If you configured the validation to run on a recurring schedule, the validation runs automatically at the next scheduled interval.
Manual, one-time run: You can trigger a run manually at any time by clicking Run Now, regardless of whether a recurring schedule is enabled.
Validata enforces a single constraint: only one run of a validation can be active at any point in time. If a run is in progress, one-time runs cannot be started and scheduled recurring runs are automatically skipped. Validata resumes scheduled execution at the next interval after the active run completes.
For details about the different execution states of a validation, see Validation Run Lifecycle States.
This section covers the following topics:
Starting a validation run: Start validations manually using Run Now or allow them to execute automatically on a recurring schedule.
Pausing and resuming scheduled executions: Temporarily suspend a validation's recurring schedule, resume paused schedules, and cancel active runs.
Monitoring validation: Track progress in real time using the live validation report, on-screen notifications, message logs, and external alerts.