Deployment Failure: Re-establish connections to activate your solution.

(1) Share

Report

Posted on by Ethan_Power

115

Please help. How do I fix this issue so I can deploy my solution from Dev to Test?

Background:

I'm trying to deploy a Solution (canvas app, model-driven app, cloud flow, multiple tables and choice lists and connection references, 1 custom connection for custom api, and more) .

Things I've tried:

Recreating the flow and model-driven app inside the solution.
Updating M365 apps in the power apps admin center
Reviewing that all connection references are active and don't show the "Fix this" button.
Removing and re-adding all required connection references.
Removing all web resources.
Reviewing/updating/changing all connection references in the flow.

Error Text:

Deploying Solution. Connections. Re-establish connections to activate your solution. 4 updates needed. The connections could not be loaded. Please try again later.

2023-08-23 17_12_46-.png

Categories:

Application Lifecycle Management (ALM)

All responses (3)

Answers (1)

NickTT 215 on at

Like (0)

Report

Deployment Failure: Re-establish connections to activate your solution.

Thanks for this! It was driving me nuts all day trying to figure out why one of the solutions was failing to import! Forgot that it had custom connecters being used in a workflow. Would be nice if Microsoft tossed an error saying "Import Custom Connector First!" and not that random one.
Ethan_Power 115 on at

Like (1)

Report

Re: Deployment Failure: Re-establish connections to activate your solution.

It worked! Thank you so much! You are the best! Love and blessings!
Verified answer

Linn Zaw Win 2,982 on at

Like (9)

Report

Re: Deployment Failure: Re-establish connections to activate your solution.

That is because you are bundling up the connection references and the custom connector for the custom API in the same solution.

When importing a solution that contains a connection reference of the new custom connector into a new environment, the import process asks for a connection to be created for the connection reference. But because the connector doesn’t exist in the new environment, the connection can’t be created.

A workaround is to put the custom connector in its own solution and then first import that to the destination environment.

This is documented under the known limitations of the custom connector.

Custom connectors need to be imported first, before connection references or flows.