Trigger Condition Test Shows 'Condition Not Met' Unexpectedly in Eve

Last updated: March 10, 2026

Overview

This article resolves the issue where the trigger condition testing panel returns "Condition not met" on matters where you expected the condition to pass. This typically occurs when configuring Auto Agents in Eve, and it indicates that Eve evaluated the test matter but determined your trigger logic was not satisfied. This can happen due to ambiguous condition language, missing baseline data, document naming inconsistencies, or overly narrow logic that doesn't match how your matters are actually structured.

Before You Start — Diagnosis

Confirm the following before attempting any fixes:

  • You have run the trigger condition test using the "Help me test this condition" panel and selected at least 3 sample matters

  • The test results show "Condition not met" for one or more matters where you believe the condition should have passed

  • You have expanded the matter rows in the test results to read Eve's full explanation of why the condition was not met

  • You have verified that the matters you tested actually contain the documents or characteristics you're testing for (for example, if testing "new medical records uploaded," confirm medical records exist in those matters)

Fixes

Possible Cause: Condition Uses Ambiguous or Relative Terms Without a Baseline

Cause: Your condition references "new" documents or "recent" uploads, but Eve has no way to determine what counts as new because there is no prior evaluation timestamp or baseline to compare against. This is especially common when testing an agent that has never run before — Eve doesn't know what was there "before" versus what just arrived.

Steps:

  1. Review your condition language for terms like "new," "recent," "latest," or "just uploaded"

  2. If testing on matters where the agent has never run, understand that Eve cannot distinguish new vs existing documents without a baseline

  3. Rewrite your condition to be more explicit — instead of "new medical records," try "medical records uploaded in the last 7 days" or "medical records in the Medical Records folder"

  4. Alternatively, specify a document characteristic that doesn't rely on timing — for example, "documents with [specific filename pattern]" or "documents in [specific folder]"

  5. Re-run the test after updating the condition

Expected Outcome: The test results now show "Condition met" on matters that contain documents matching your revised, explicit criteria. Eve's explanation confirms it found the documents based on the specific logic you provided (folder name, date range, or other concrete filter).

Possible Cause: Folder or Document Names in Condition Do Not Match Actual Matter Structure

Cause: Your condition references a folder name or document type that does not exist in the test matters, or the naming is inconsistent across matters. For example, your condition checks for "Discovery" folder but the actual folder is named "DISCOVERY RECEIVED" or "Disc Responses." Eve treats condition text as exact — it will not infer or fuzzy-match folder names.

Steps:

  1. Open one of the test matters that returned "Condition not met"

  2. Navigate to the matter's document structure and verify the exact folder names and document titles

  3. Compare these exact names to what you wrote in your condition

  4. If there is a mismatch, update your condition to use the exact folder or document name as it appears in the matter

  5. If folder naming varies across matters (for example, "Medical Records" in some matters and "MedRecs" in others), revise your condition to account for both variations using OR logic — for example, "documents in Medical Records OR MedRecs folder"

  6. Re-run the test after correcting the folder or document names

Expected Outcome: The test results show "Condition met" on matters where the folder or document name now matches exactly. Eve's explanation confirms it located the specified folder or document type in the matter.

Possible Cause: Condition Logic Is Too Narrow or Overlapping

Cause: Your condition includes multiple filters that are too restrictive when combined, or you're checking for a combination of criteria that rarely occurs together in practice. For example, "new medical records uploaded to Billing folder within the last 3 days" may be technically correct but so specific that it almost never evaluates to true.

Steps:

  1. Review your condition and identify how many filters you've applied (document type + folder + recency + other criteria)

  2. Temporarily simplify the condition by removing one filter at a time — for example, remove the folder restriction or extend the time window

  3. Re-run the test after each simplification to see which filter is causing the condition to fail

  4. Once you identify the restrictive filter, decide whether it's necessary — if the filter is essential to your use case, verify that it accurately reflects how documents are actually organized in your matters

  5. If the filter is not essential, remove it or broaden it to make the condition more flexible

  6. Re-run the test with the revised condition

Expected Outcome: The test results show "Condition met" on matters where the simplified or broadened logic now applies. Eve's explanation confirms it found documents that satisfy the less restrictive criteria.

Possible Cause: Test Matters Do Not Contain Qualifying Documents or Activity

Cause: The matters you selected for testing genuinely do not satisfy your condition — not because the condition is wrong, but because those specific matters don't have the documents or activity the condition is looking for. This is a valid test result, not a failure.

Steps:

  1. Review the matters you selected for testing

  2. Confirm whether those matters actually contain the documents or characteristics your condition is checking for — for example, if your condition is "new medical records uploaded," verify that medical records were in fact uploaded to those matters recently

  3. If the test matters do not contain qualifying documents, select a different set of test matters that you know should satisfy the condition

  4. Re-run the test with the new matter selection

  5. If you still see "Condition not met," return to the other possible causes above — the condition logic itself may need refinement

Expected Outcome: When you test on matters that genuinely contain the documents or activity your condition is checking for, the test results show "Condition met" and Eve's explanation confirms it found the expected documents. If the condition is correctly written, "Condition not met" on matters without qualifying documents is the correct and expected result.