It's likely that the problem has to do with how Power Automate maps and caches link references within a solution. Try below steps for troubleshooting and possible solutions for this issue-
Open your solution in Power Automate.
Check the "Connection References" section and confirm each reference is linked to the correct connection.
In your flow, find the action using the "HTTP with Entra ID" connector.
Temporarily change the connection reference to another one, save the flow, then switch it back to the correct connection reference and save again.
Rename the connections in Power Automate or Azure Portal to make them unique (e.g., Function1_Connection
and Function2_Connection
).
Delete unused or duplicate connections in the Power Automate "Connections" section.
If the issue still happens, export your solution, import it into a new environment, and create fresh connection references linked to unique connections.
Test each connection separately in its own flow to confirm they work as expected.
stampcoin
97
Michael E. Gernaey
70
Super User 2025 Season 1
David_MA
48
Super User 2025 Season 1