How to Test and Validate Agent Trigger Conditions in Eve

Last updated: March 10, 2026

Overview

This article shows you how to test your agent's trigger condition before it goes live to ensure it will fire correctly on the right matters. Testing validates that your trigger logic works as intended and helps you catch issues like overly broad conditions, overly narrow conditions, or naming inconsistencies before the agent starts running automatically across your firm's matters.

Prerequisites

  • You must be a Firm Admin to configure and test triggers for Auto Agents

  • You must have already started creating or editing an agent and entered a trigger condition in the "When to Run" field

Step-by-Step Instructions

  1. Expand the Testing Panel — After entering your trigger condition in the "When to Run" field, click "Help me test this condition" to open the testing panel. This panel allows you to validate your trigger against actual matters before activating the agent.

  2. Select Matters to Test Against — You have two options for choosing test matters: click "Select matters" to manually choose up to 5 specific matters from your case list, or click "Random pick" to let Eve select a random sample from your matters. Eve recommends testing with at least 3 matters to get a meaningful read on whether your condition logic is working as intended.

  3. Run the Test — Click "Test condition" to run the evaluation. Eve will check each selected matter against your trigger condition and return results for all of them.

  4. Review the Results for Each Matter — For each matter tested, Eve will show one of two results: "Condition met" means the trigger would have fired on this matter and the agent would have run, or "Condition not met" means the trigger would not have fired. Eve provides a detailed explanation for each result, telling you exactly what it found or what information was missing.

  5. Read Eve's Explanations Carefully — The explanation Eve provides is detailed and transparent. For example, if your condition is "new medical records are uploaded" and Eve cannot determine what counts as "new" on a given matter, it will tell you exactly why — such as the absence of a prior-evaluation timestamp or ambiguity in which files were recently uploaded versus previously existing. Use these explanations to understand whether your condition is working correctly.

  6. Refine Your Condition Based on Test Results — If you see "Condition not met" on matters where you expected the agent to run, read Eve's explanation to identify what's missing or ambiguous. Common issues include overly broad conditions that would fire on the wrong matters, overly narrow or ambiguous conditions that Eve can't reliably evaluate, or naming inconsistencies across matters (like discovery files named "ROGS," "Interogs," or "Interrogatories"). Adjust your condition to be more specific about where Eve should look, reference exact folder names, and anticipate naming variations by building them into your condition using AND/OR logic.

  7. Re-Test Until Results Match Your Intent — After refining your condition, run the test again with the same or different matters. Continue testing and adjusting until you see consistent, expected results across your sample matters. When "Condition met" appears on the right matters and "Condition not met" appears on matters that should be excluded, your trigger is ready to activate.

Best Practices for Writing Testable Trigger Conditions

  • Be specific about where Eve should look — Reference a folder name (for example, "in the Discovery folder") when relevant to narrow the scope

  • Anticipate naming variations — Build variations into your condition (for example, "files named ROGS, interogs, or interrogatories") to catch all possible naming patterns across matters

  • Use Eve's explanations as a guide — If your condition returns "not met" unexpectedly, read Eve's explanation carefully — it will usually tell you exactly what information is missing or ambiguous and point you toward the fix