Answered

Flow stuck on PowerApps (V2) Trigger

(0) Share

Report

Posted on by JChouinard2016

Hello,

I'm running a flow to create a new document in a sharepoint library. When I trigger the flow from my powerapps button, it either gives me error 502 bad gateway, or it runs and gets stuck on the trigger like so:

I'd appreciate any help or suggestions.

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (1)

PowerPuffKK 316 on at

Like (0)

Report
Copy link

Link copied!

Hi @JChouinard2016,

Sometimes it can be a bit of caching on the Power Apps side causing the 502 Bad Gateway if you've edited the flow since it was added to the app.

Have you tried removing the flow from your app and re-adding it back in? This has helped me in the past with the 502 error.

If this answer helps, please mark it as a solution for future forum visitors.

Thanks
Kristine 😊

Was this reply helpful? Yes No
Verified answer

JChouinard2016 56 on at

Like (1)

Report
Copy link

Link copied!

@PowerPuffKK ,

What you suggested was part of the solution.

I ended up doing these steps:

- Removed flow from the app in the power automate pane.
- Added flow back to the app in the power automate pane.
- Opened the flow in the power apps / power automate editor and saved the flow.
- Cut the trigger 'FlowName'.Run(.....) from the code in my app and pasted it back to the same spot to refresh the trigger.
- It worked.

I was working between power automate online and powerapps, so something must have occurred when I saved the flow in power automate online. It gave me a warning that my flow might break, but following the steps above seemed to fix it.

Thanks for your help.

Was this reply helpful? Yes No