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?
Solved! Go to Solution.
I don't know if this is an ongoing issue. My recollection is that I just had to recreate the entire Flow and try again. I don't believe that I ever understood what was wrong with the Flow that would not register, so I cannot try to reproduce to test.
Hi @Anonymous , @jadm
I have just experienced this problem again. I have a quite complex Flow for an approval process that was all working and now it just won't start from my PowerApp. It started coming up with a runtime error "trigger is not enabled" which I have not been able to find any information about.
I then removed the Flow from my app and now I have the dreaded "Failed to Register Service" error when I try to register the Flow again.
Please advise what steps I can take to try to fix this? I see other posts here talking about the problem being with the auto generated JSON schema. Can anyone help me with looking at this?
Hi @Anonymous and @jadm ,
I have managed to register the Flow now. I tried the suggestion of exporting the Flow and then reimporting it again as an update, and that seemed to fix the problem.
We are having the same issues with registering our Flows here... What I have found is if you have different connections, we have multiple people using their own connections while building, the service will not register. Once the connections in Flow have been changed to person registering the Flow in PowerApps, everything registers correctly.
Exporting and re-importing a Flow will request access to a connection when you open the Flow up, hence re-establishing the connection to the logged in user.
Mannually - Make sure to change the connection in each step of the Flow to the person who is registering the Flow in PowerApps, save the Flow, refresh PowerApps, connect the Flow to the item in your PowerApp, everything should register correctly.
Check out new user group experience and if you are a leader please create your group
Did you miss the call?? Check out the Power Apps Community Call here!
ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.