Custom connector: This operation is being provisioned. Please try again in a few minutes.

[NielsL]

I'm trying to create a custom connector for HubSpot. 

However, I keep getting an This operation is being provisioned. Please try again in a few minutes' error. Does anyone how long a 'few minutes' are in Power Automate terms? It has been like this for more than an hour now. 

The GET request and response works fine when I test it on the HubSpot Developer site so that does not seem to be the issue. 

Do I just need to be more patient? 🤨

[CFernandes]

@NielsL 

Hey Mate,

You will need to wait for some time and check if the connector has been provisioned. 

In the past I had the same problem, and the solution for me was to  Deleted and rebuilt the Custom Connector again.

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!

[NielsL]

I tried creating a V2 of the connector yesterday. I just checked this morning, and I'm getting the same error for both custom connectors.

Could DLC policies affect this somehow? E.g. if a certain Azure connector is blocked?

[TomPhillips]

Did you find a resolution to this? I'm experiencing the same issue, weird thing is that is was working initially this morning

[NielsL]

@TomPhillips unfortunately not. I was working for for a short period of time - but then I started getting the error again. 

[Imke]

Had this error as well and the reason was really stupid. Leaving this here for my future self or others:

I had copied the URL for the endpoint from the Microsoft page and didn't realize that the "GET" already came with it.

So ended up with an invalid URL in the Request Definition area. It didn't trigger a validation error, so it took me quite a while to figure out:

so a real basic error, but the error message when testing was a bit misleading imo.

[poweractivate]

@NielsL 

I could reproduce this issue as you did for new Custom Connector creation attempts in specific windows of time in October 2020. This may still mean it affected only me and you, and not others, but I wanted to let you know, that I was able to reproduce exactly this issue.Not using any VPN and everything else was correct about setup (at least I believe that to be so).

I could reproduce this exact issue in some specific windows of time in October 2020. I would emphasize that it only affected creation of new Connectors. At no time could I find any existing custom Connectors on any tenant at all whatsoever that was down or otherwise affected. Also, during that window of time, I could freely modify any Custom Connector as long as they were created prior to some specific window of time, or maybe even during that window of time "if lucky". Even during the window of time that I reproduced this issue, no existing Custom Connectors were down, and no existing Custom Connectors lost any freedom to be modified . 

As of the original date of this writing, and also as of a few days ago, I no longer get this specific issue anymore, I can create new Custom Connectors now. However, I did happen to stop using this feature for new Connectors entirely for some time after I noticed this issue, and only focused on existing, already created Custom Connectors for quite a while. It is possible that if there was any issue, it may have been fixed far earlier than when I recently attempted to create a Custom Connector again a few days ago from the original date of this writing.

I do not know exactly the details on if there was an actual issue in the platform, who it affected, and when it was resolved. All I could say is as of this writing, it worked for me now, but that I was able to reproduce the issue in some specific windows of time in October 2020.

Check if the above helps @NielsL 

[brentlightsey]

Huge help on this one! I did the same thing and this fixed it up.

[rbunge]

Wondering if anyone made any progress on this -- unlike brentlightsey, ours was not a URL issue... twice now we have received this error, and we found the way to fix it was to click Update Connector. Problem is, not all users have access to do so. Once the admin updates it, connector functions normally again. Doesn't seem to be rhyme or reason.

[mr_steve]

This might help: HubSpot CRM (Independent Publisher) - Connectors | Microsoft Docs

[poweractivate]

@rbunge 

The original post talked about an error, which I remember getting at that specific window or time-frame, even with the URL being correct, which I have reason to believe just went away shortly after. 

Did you still receive this exact error as in the original post on around June 18, 2021?

If so, did it only affect brand new connector, or did it ever happen when existing a previously deployed connector?

I would be curious if for some reason the issue occurred again, as I did not see it occur again after that specific window of time in the original posting. After December 2020 I never got the error again, and I suspect the error wasn't there from earlier than that. I only got the error in some specific windows in time in October 2020 and this happened even if the URL was correct - but it did not happen again to me after that. Even during that window of time in October 2020, all my existing Custom Connectors on all tenants were still working and also could be edited, it was only the attempt to make brand new from-scratch Custom Connectors which were affected and showing this error persistently at that time.

Are you still getting this issue? If so I'd be curious of the details of the issue and do you also get the issue recently as well?

[shankarb]

I am getting the same exact error when I am creating a custom connector for an API from an API management, did anybody get resolution to this problem ?

Error message:  This operation is being provisioned. Please try again in a few minutes.

[dougOfLa]

New to Power Apps - not to APIs  -- I keep getting the same problem "This operation is being provisioned. Please try again in a few minutes."    

I can hit the API using postman and do just about everything else accept use the API in Power Apps.    I am trying to just find a quick - easy to use low code environment .   Is powerApps really this hard  (or buggy) to use?

I have tried deleting the connector, updating the connector.  Neither of these operations are successful.   

Postman was easier to use.

[rob_at_opinyin]

I had this issue and found that it was because I had operations with query parameters that were set to required and I was not providing them.

I created a connector from a postman collection and this automatically set up all the query parameters as required even when some are not.

As previously stated the error message is unhelpful but once I worked out what the issue was it was easy to fix by just switching to the Swagger Editor and changing the required value to false for the endpoints that were optional.

[DaveChristensen]

I too encountered this problem.  In may case the URL required a numeric parameter (latitude, as it happens).  I put in a value of 1.9 and hit test, and got the operation is being provisioned error.  What actually happens is that the test harness doesn't URLEncode the parameters, and gets some random error as a result which it misleadingly translates into the provisioning error.  If I use 1%2E9 as the parameter, it works perfectly.

This is clearly a bug in the test harness which will be misleading many people - where do we raise this to get it fixed?