Power Automate · Cloud flows: runtime expression errors

ExpressionEvaluationFailed

Short answer

ExpressionEvaluationFailed in a Power Automate cloud flow: An expression failed to evaluate at runtime because the actual data didn't match what the expression expected. This error only occurs when the expression uses **dynamic values** (variables, trigger body, action outputs) that can't be checked at save time. The most likely fix is to add null checks, validate types.

VerifiedLast verified

01Error text

Power Automate error
ExpressionEvaluationFailed

02Likely causes

  • Calling int() on a variable that contains a non-numeric string at runtime
  • Accessing a property on a null object (outputs('Get_item')?['body/title'] when Get_item returned nothing)
  • Date format mismatch in formatDateTime() or parseDateTime() when the format comes from a variable
  • Division by zero when the divisor is a dynamic value that happens to be 0

03How to fix it

  1. Open the failed run and select the failed action to display the expression and input values.
  2. Wrap risky expressions with null checks: if(empty(triggerBody()?['value']), 'default', triggerBody()?['value']).
  3. Use coalesce() to provide fallback values: coalesce(outputs('Get_item')?['body/title'], 'Untitled').
  4. Validate data types before conversion: if(isInt(variables('input')), int(variables('input')), 0).

iNotes

If an expression uses only constant values (like int('abc') or div(100, 0)), the flow engine catches the error at save time as InvalidTemplate instead.

04Official documentation

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

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.