Hi all,
We are running into an issue with connection references and custom connectors across environments, and would appreciate any guidance.
Context:
We are deploying a managed solution (Core Build) across environments (Dev → UAT → Prod) which includes:
-
A custom connector: Stripe - Donations Connector
-
A connection reference used by flows
Issue:
In one environment(PRD) , when trying to assign a connection to the connection reference, the dropdown shows no available connections, even though:
-
The custom connector exists
-
Multiple connections have been created successfully
-
Connections are shared with users and service accounts
Investigation:
-
In the Custom Connector → Test tab, connections are visible and usable
-
However, in the connection reference screen, the Connector field appears blank or does not match
-
It appears that the connection reference is pointing to a different connector ID than the actual connector in the environment
-
The connector and connection reference were created at nearly the same time, which may have caused a mismatch
Comparison:
-
In other environments (UAT ), this works correctly
-
In those environments, the connector was created before the connection reference
Constraints:
-
The solution is managed, so we cannot modify or recreate the connection reference
-
We want to avoid creating unmanaged components or editing managed flows
Question:
Has anyone encountered a connector ID mismatch between a connection reference and a custom connector?
Is redeploying the solution the only supported fix?
Is there any way to rebind or repair the connection reference without recreating it?
Any help or confirmation would be greatly appreciated. Thanks!

Report
All responses (
Answers (