cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Series of unusual errors

Hi, I'm on step 3 of creating a custom connector (Definition).

When I click Create connector, first I get error:

Encountered internal server error from Azure Resource Manager. The tracking Id is 'b4009573-f124-448c-81e5-f5afd1ad3f01'.

 

Then when I try again, I get the message:

'Connector already exists'

 

I'm not sure where all these connectors are being saved.

After a couple of attempts, a connector is finally saved (I got to version 3 of the naming convention) but when I test it, I get an error 

'Request failed. Please try again in a few minutes."

1 REPLY 1
v-yamao-msft
Community Support
Community Support

Hi @Anonymous,

 

I have seen the same issues on other threads. A workaround I got is “Strip incoming swagger file of any tags if you don’t need them”.

Please take a try with it.

Further, please check the following doc for a reference on Create a custom connector from an OpenAPI definition:

https://docs.microsoft.com/en-us/connectors/custom-connectors/define-openapi-definition

I will try to help report it on my side.

 

Best regards,

Mabel

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

New Process Advisor Capabilities carousel.png

Read the blog for the latest news

Read the latest about new experiences and capabilities in the Power Automate product blog.

PA Survey Carousel Image.png

We want to hear from you!

If you are a small business ISV/Reseller, share your thoughts with our research team.

Top Solution Authors
Users online (2,251)