Unanswered

Flow connected to powerapp suddenly stops working

(0) Share

Report

Posted on by CedricOsei

Hi there,

over the past year I have been developing and managing a Powerapp. Unfortunately there are times when the powerapps connected flows stopp working for some users without any implication of any triggering (This phenomenon is often met with a 502 code error in the banner of the app).

Even though I could resolve the problem temporarily, I definitely am still on the quest for a more sustainable way to guarantee the functions of the powerapp.

Is there any way to detect such failing setups in an app without user feedback (since the Powerautomate logs indicate no triggering of the powerautomate)? Additionally I wanted to ask whether I am doing something wrong on my end encapsulating app, automate and components in a solution and importing the latest version of the solution to the PROD enviroment?

I look forward to hearing your Ideas and answers.

Categories:

Using flows

All responses (2)

Answers (0)

Sort by

Manish Solanki 15,169 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @CedricOsei

Many a time the flow becomes turn off due to inactivity after 90 days. To handle those cases, we can set up monitor flow that can turn suspended flows back on using power automate for admin connector.

Here is a sample flow:

We will set up a schedule flow for monitoring purpose and using "Get flow" action get the metadata of the flow:

Next, check the state of the flow and if found suspended then turn it on using "Turn on flow" action

This way we can turn on the suspended flow automatically with no or minimal down time.

If this helps & solves your problem, please remember to give a 👍 and accept my solution as it will help others in the future.

Thanks
CedricOsei 11 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @ManishSolanki,
the app itself and flow is usually used on a daily basis, hence I am not sure if it will also fall into the 90 days inactive range for the suspension. Additionally I am not sure if the flow is also tagged as suspended in my case, since the flow is triggered properly when I personally (as developer and one of the owners of the app) trigger the button.

I will definitely try and monitor the status of the flows of the app through your mentioned approach!