# 9.14 - Validation Workbench - Knowledge Base

Validation Workbench - Knowledge Base — Knowledge Base articles.

# Validation Workbench (Knowledge Base Articles)

## Contents

- [Validation Workbench](/books/validation-workbench-knowledge-base/page/validation-workbench)

What is the reason for some of the validations not getting triggered even when the validation conditions meet?

<u>Response:</u>

There is a timeout to confirm if the element is present, usually 2 seconds, otherwise, the validation will not get triggered

This is important because we cannot wait indefinitely for the element to appear on the page.

IT is a tradeoff meaning a very small case of validation will not get triggered BUT the speed of the test will not be affected significantly when adding validations. This is a VALID approach in AJAX environment like Browser JS, image as a button not appearing when loading a UI, it is a common case.

<div id="bkmrk-last-updated%3A-june-0">---

Last updated: <span class="mc-variable General.NewDateTimeVariable variable">June 02, 2023</span>

If you have any feedback on this topic, please contact us at <documentation@appvance.ai>

</div>

# Validation Workbench Knowledge Base Overview

**Last reviewed:** September 30, 2026

Use this article as the maintained overview for Validation Workbench concepts, triggers, validation types, CSV-driven validations, and AISG usage.

## What changed in this article

- Consolidated a long legacy Validation Workbench page into a current knowledge-base overview instead of repeating every old screenshot-driven procedure.
- Replaced Test Designer/BP wording with Scenario Editor and AISG terminology while preserving .valid file, trigger, validation type, and CSV-driven concepts.
- Added practical checks for trigger scope, performance impact, manual validations, reusable files, and evidence in AIQ results.

## Validation workflow

1. Define the validation goal, trigger condition, validation type, and pass/fail rule before adding it to a .valid file.
2. Choose manual or targeted triggers for expensive validations so every step does not perform unnecessary checks.
3. Run the related Scenario Editor or AISG workflow and confirm validation names, pass/fail status, and evidence are visible in results.

**Review note:** This page overlaps with the shorter Validation Workbench overview but remains as the KB-level reference.

---

Last updated: September 30, 2026

If you have feedback on this topic, contact <documentation@appvance.ai>.