Answered

"Failed to register service" error continues

(0) Share

Report

Posted on by mcorning

332

I havbe yet to get a simple Flow that starts with a PowerApps trigger and calls an HTTP POST. When i try to add the Flow to my PowerApp, i still see the subject error.

there is hard wired json in the body of the Http Action, though i will eventually need to pass two strings from the PowerApp.

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (1)

v-yamao-msft on at

Like (0)

Report

Hi Mcorning,

It seems that you are adding a flow to PowerApps. How is your flow configured? Could you send me a screenshot of your flow configuration?

Your flow is now triggered by “PowerApps”, could you please try to change the “PowerApps” trigger to another one to see if it works?

Best regards,
Mabel Mao

Was this reply helpful? Yes No
mcorning 332 on at

Like (1)

Report

her are the screen shots you asked for.

i'm not sure what you mean about trying another trigger. i have a separate issue here in the Forum about using a PowerApps trigger on CDS Get record action. or did you mean drop the PowerApps trigger and create a new PowerApps trigger?

PowerApps ErrorFlow definition that fails to start

Was this reply helpful? Yes No
v-yamao-msft on at

Like (0)

Report

Hi Mcorning,

I create a similar flow with you, when I add the flow to a button on an App, I can add the flow with no error message.

Please try to add a button on your App then add the flow to this button to see if this works for you. Please also make sure the flow is in the same environment with you App.

This article could also be a reference for you:
https://powerapps.microsoft.com/en-us/tutorials/using-logic-flows/

Best regards,
Mabel Mao

Was this reply helpful? Yes No
Verified answer

mcorning 332 on at

Like (0)

Report

I created a new flow with a PowerApps trigger and an Http Action. this time i let the PowerApp send the url to the GET. Btw, is there a reason the Http Action includes a Body field for GET methods?

this new flow did not return the failed to register error, and nothing i could do to my original flow could rehabilitate it, so i removed it. Perhaps the issue was a vestige from flows of weeks past. In any case, i cannot repro my original error.

i will create a new thread given what i found when i passed http://microsoft.com to the Http Get...

Was this reply helpful? Yes No