Showing results for 
Search instead for 
Did you mean: 
Not applicable

Failed to register the service

I have a working flow (tested in the Flow Studio via "Test" button), also I have a PowerApp, which contains a button, by clicking on which the flow should start running. So these 2 pieces seem to work separately from each other, but once I try to connect the flow to my app, via clicking [Action -> Flows -> click on my flow] I am getting the error message saying "Failed to register the service". Please check the attached screenshot for the details. Does anyone know what is the issue?

Not applicable

Hi All,


Please review the following thread that has been marked a solution regarding "register error with flow".


If this does not solve your problem, please reply back in this thread. 



Not applicable

Hi @Anonymous,

The thread that you have linked to does not have a solution at all for the issue that people have raised in this thread. The solution was to not use a Flow at all. The issue we have had is that sometimes the Flow just won't register to a Powerapp. When this happens, you have no idea why, and don't know how to start resolving it. Microsoft needs to help people understand what causes this issue, not see how people solved their particular problem by doing something different.

PowerApps is a great product, but when something doesn't work it can be a very frustrating experience to try to debug it.

Not applicable

Thanks for your reply @Anonymous. Will research for a solution that solves your specific issue. 



Not applicable

Hi @Anonymous,

It would be much more useful if you could explain what the causes are getting this error. I can't even remember what my specific issue was because I think I just had to do it a different way because I could not get the Flow to register and I had no information about why. Surely Microsoft has some idea of what causes this issue?




Frequent Visitor

The fix is to export and re-import the flow again  using the update function ( not the create as new), this should resolve your issue hopefully 

View solution in original post

Frequent Visitor

Unfortunately your suggestion doesn't work -

I've tried:

Create new from Flow

Export and then import, update existing flow

Export and then import, create new flow

Create new flow from powerapps


Nothing works, always get the same generic regsitering error.

Hi @jadm 


I have ahd this problem and the only way to fix it was to get the creator of the flow (who needs co-author access) to peform the operation.


THis worked for me.  Nothing else did even if I was a co-author of the flow.





Frequent Visitor

I'm glad that worked for you. I am the creator.


However, for what its worth, I realised the auto generated JSON schema (I was using response-request action) was missing some data types for some coloumns. Once I filled those in it registered happily.


Been chasing this bug for good 3-4 hours Smiley Frustrated

Not applicable

@jadm @Anonymous  @Anonymous  @NigelP  @IrhanC  Are we still have issues with this?


Frequent Visitor

TLDR - yes it is.

In my case the auto-generated schema was the culprit and fixed quite easy. However, figuring out THAT was the issue took hours.

Providing a more useful/specific error message would go a long way, rather than a generic "failed to regsiter service".

... or hardening the auto create schema function.


Thx for following up.


Helpful resources

UG GA Amplification 768x460.png

Launching new user group features

Learn how to create your own user groups today!

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

M365 768x460.jpg

Microsoft 365 Collaboration Conference | December 7–9, 2021

Join us, in-person, December 7–9 in Las Vegas, for the largest gathering of the Microsoft community in the world.

Top Solution Authors
Top Kudoed Authors
Users online (1,149)