Views:

Applies to Product - Power Apps

What’s happening?
Customers are experiencing failures when attempting to send emails through custom-built Power Apps and Cloud Flows, resulting in error messages related to connection issues and token expiration.
 

Reason:

  1. The email failures in custom-built Power Apps are often caused by the app not updating to reflect changes made in the flow, particularly when the flow was updated to use a new connection while the app retains the old flow metadata.
  2. In Cloud Flows, the error "Runtime call was blocked because connection has error status: Enabled| Error" typically occurs due to expired refresh tokens, which can happen when connections are not used for 90 days, leading to security measures that block access.

 

Resolution:

  1. For Power Apps:
  2. Open the app for editing using the latest version of the studio.
  3. Remove the flows from the app by accessing the data sources pane and removing each flow.
  4. Re-add the flows to the app.
  5. Save and republish the app to ensure changes take effect.
  6. For Cloud Flows:
  7. Ensure the mailbox is licensed and active by checking in Microsoft 365 Admin Center.
  8. Enable the API (OWA & EWS) for the mailbox using the following PowerShell commands:
    • Set-CASMailbox -Identity <MailboxIdentity> -OWAEnabled $true -EWSEnabled $true
  9. Remove any application access policies that may be blocking API access using:
    • Remove-ApplicationAccessPolicy -Identity <PolicyName>
  10. Verify that Modern Authentication is enabled:
    • Check with Get-OrganizationConfig | Format-Table -Auto ModernAuthentication
    • If disabled, enable it with Set-OrganizationConfig -OAuth2ClientProfileEnabled $true
  11. Restart Power Automate and retry the email flow.
  12. Use Microsoft Graph API to test if the mailbox is accessible with:
    • Test-MAPIConnectivity -Identity <MailboxIdentity>
  13. If the issue persists, consider re-authenticating the connection in the flow to refresh the access token and resolve the error status.