Power Automate · Cloud flows: trigger errors
TriggerConditionNotMet
Short answer
TriggerConditionNotMet in a Power Automate cloud flow: The trigger evaluated its condition and determined the event shouldn't start a flow run. The most likely fix is to review trigger condition expression.
VerifiedLast verified
01Error text
TriggerConditionNotMet02Likely causes
- A trigger condition expression always evaluates to false (logic error)
- The trigger condition references a field that doesn't exist in the trigger payload
- The event occurred but the data didn't match the filter (for example, "When an item is created" with a condition on Status, but Status was blank)
03How to fix it
- Go to the trigger's Settings and review the trigger condition expression.
- Test the condition against a known event payload. Use Peek code on the trigger to display the raw schema.
- Temporarily remove the condition, trigger the flow manually, and inspect the trigger output to verify field names and values.
- Fix the expression and re-enable the condition.
04Official documentation
→Related errors
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Power Automate work:Open Power Automate jobs