Updating Power Automate Connections Breaks Power Apps

Updating connections in a Power Automate flow can break linked Power Apps. Learn why this happens and the steps to fix it so your app works again.

Here’s the scenario. You have a canvas Power App that uses a Power Automate flow. The app triggers the flow, it does something, then returns the result to the app (or maybe not). You have both the app and workflow in a Solution.

You’ve deployed the solution to the Test and possibly Production environment. Everything is functioning.

Later, you update your connections in your Power Automate workflow. Perhaps you added something new or realized you want it to use a Connection Reference created in your Solution. In either case, you make updates, test the workflow, and everything seems fine.

You retest your Power App in Dev, and everything functions correctly.

Next, deploy to the Test environment. You get errors! The Power App can’t trigger the workflow.

Why does this occur?

Changing the connections in your Power Automate workflow alters the trigger schema. Your Power App sees the original schema of the workflow at the time it was imported.

The Solution.

If this scenario applies to you, update the Power Automate workflow schema from your Power App.

After updating a workflow connection, you need to:

• Edit the Power Apps using that workflow.
• Open the Power Automate panel.
• Remove the Power Automate workflow from your app.
• Add the same Power Automate workflow back into your app.
• Test
• Deploy
• Test in the next environment.

The steps should reset the schema and everything should be good.