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.
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
P.S. take a look at my blog here and like & subscribe to my YouTube Channel thanks.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.