Trigger condition failed – Trigger conditions set in the flow did not match incoming data.

Power Automate allows users to set trigger conditions to ensure that a flow runs only when specific criteria are met. However, you may encounter the following error:

“Trigger condition failed – Trigger conditions set in the flow did not match incoming data.”

This means that the incoming data did not satisfy the defined trigger condition, preventing the flow from starting.

---

2. Causes of “Trigger Condition Failed”

Several reasons can cause a trigger condition to fail:

1. Incorrect Expression Syntax – If the trigger condition contains syntax errors, it may not evaluate correctly.
2. Data Mismatch – The incoming data does not match the expected format, type, or value.
3. Null or Missing Data – If the trigger condition depends on a field that is missing or empty, the condition will not pass.
4. Case Sensitivity Issues – String comparisons in Power Automate are case-sensitive by default.
5. Boolean and Number Comparisons – Misinterpreting true/false values or numeric conditions can cause failures.
6. Dynamic Data Not Available at Trigger Time – Some fields might not be populated when the trigger evaluates the condition.
7. Logical Errors in Conditions – Using AND (&&) or OR (||) incorrectly can prevent conditions from passing.
8. Environment-Specific Issues – Some flows behave differently in different Power Automate environments due to data governance or policy restrictions.

---

3. Step-by-Step Troubleshooting Guide

Step 1: Check Flow Run History for Condition Details

1. Open Power Automate (https://flow.microsoft.com).
2. Navigate to My Flows and locate the affected flow.
3. Click on Run History to review failed runs.
4. Look for the error message under Trigger Condition Failed to identify which condition did not match.

Example of Expected Data in Run History:

{
  "Status": "Active",
  "Priority": "High",
  "Category": "Urgent"
}

Example of Incoming Data That Doesn’t Match Condition:

{
  "Status": "Inactive",  // Doesn't match "Active"
  "Priority": "Low",     // Doesn't match "High"
  "Category": "Normal"   // Doesn't match "Urgent"
}

---

Step 2: Verify Trigger Condition Syntax

Trigger conditions in Power Automate follow Power Fx syntax or Expression Builder logic. Ensure that the condition is correctly formatted.

Correct Example:

plaintextCopyEdit@equals(triggerBody()?['Status'], 'Active')


Incorrect Example (Missing Quotes, Case Sensitivity Issue):

@equals(triggerBody()?['Status'], Active)  // ❌ Missing quotes around 'Active'
@equals(triggerBody()?['status'], 'Active')  // ❌ Field name is case-sensitive

---

Step 3: Confirm the Field Exists in Incoming Data

• If a field is missing in the trigger data, the condition will fail.
• Use null checks to prevent errors when the field is absent.

Correct Example (Handles Missing Field):

@and(equals(triggerBody()?['Status'], 'Active'), not(empty(triggerBody()?['Priority'])))

Incorrect Example (Fails If ‘Status’ or ‘Priority’ Is Missing):

@equals(triggerBody()?['Status'], 'Active')

Solution:

• If a field might be missing, use coalesce() to provide a default value.

plaintextCopyEdit@equals(coalesce(triggerBody()?['Status'], 'Unknown'), 'Active')

---

Step 4: Validate Data Type Compatibility

Power Automate is strict about data types (string, number, boolean). If the condition is checking a number as a string, it may fail.

Correct Example (Ensuring Number Comparison Works):plaintextCopyEdit@greater(triggerBody()?['Amount'], 1000)


Incorrect Example (Comparing String Instead of Number):

@greater(triggerBody()?['Amount'], '1000')  // ❌ '1000' is a string, not a number

Solution:

• Convert a field into a number using int() before comparing:

plaintextCopyEdit@greater(int(triggerBody()?['Amount']), 1000)

---

Step 5: Consider Case Sensitivity in String Comparisons

Power Automate comparisons are case-sensitive by default. Ensure string comparisons match the exact case.

Correct Example (Using Lowercase for Case-Insensitive Matching):

@equals(toLower(triggerBody()?['Category']), 'urgent')

Incorrect Example (Fails If Case Doesn’t Match Exactly):

@equals(triggerBody()?['Category'], 'Urgent')  // ❌ Fails if incoming data is 'URGENT'

Solution:

• Convert both the trigger field and condition value to lowercase using toLower().

---

Step 6: Review Logical Operators (AND, OR)

Ensure that AND (@and()) and OR (@or()) conditions are used correctly.

Correct Example (Both Conditions Must Be True for Flow to Run):

@and(equals(triggerBody()?['Status'], 'Active'), equals(triggerBody()?['Priority'], 'High'))

Incorrect Example (Misusing AND and OR):

@and(equals(triggerBody()?['Status'], 'Active') or equals(triggerBody()?['Priority'], 'High'))

Solution:

• Use @or() if the flow should run when either condition is met.

@or(equals(triggerBody()?['Status'], 'Active'), equals(triggerBody()?['Priority'], 'High'))

---

Step 7: Test Trigger with Sample Data

1. In Power Automate, go to your flow.
2. Click Edit and open the trigger condition.
3. Click Test and select Manually Triggered Flow.
4. Provide sample data to check if the trigger fires correctly.

---

Step 8: Remove and Reapply the Trigger Condition

• If everything looks correct but the trigger still fails, try:
  1. Removing the trigger condition temporarily.
  2. Saving the flow and re-enabling the trigger.
  3. Reapplying the condition and testing again.

---

4. Preventative Measures

To avoid “Trigger Condition Failed” issues in the future:

✔ Use coalesce() to handle missing fields.
✔ Convert strings to lowercase for case-insensitive checks.
✔ Ensure number comparisons treat values as numbers.
✔ Use test runs to validate conditions before deployment.
✔ Double-check logical operators (@and(), @or()).