An issue combining Flow and Power Apps Custom API

Unexpected side effect from changing a custom API that was being called from a flow

Unexpected side effect from changing a custom API that was being called from a flow

Scenario

Solution contained:

  • custom API
  • a solution-based PowerAutomate flow that called the custom API

Solution was being created as unmanaged in one environment, then deployed as managed into production.

What changed?

  • Made a change to the custom API (added additonal optional parameters)
  • redeployed the solution

What was the impact?

  • on deployment of the change, the flow stopped working in the target environment where the solution was deployed as managed, and all attempts to turn it on failed
  • it became impossible to edit the flow in the unmanaged development environment (screen timeouts)

Solution

  • remove the additional API parameters
  • redeploy the solution as an upgrade in order to remove ther copy of the parameters ina lower layer in the target environment
  • turn on the impacted flow in the target environment (which now worked again)
Avatar
Proactive application of technology to business

My interests include technology, personal knowledge management, social change

Related

Next
Previous