I have a few flows in Prod that stopped showing the run history in Power Apps, but if I go to the Power Automate Automation Center and look at Run History they show up as expected. Flow runs from yesterday and before are still showing in Power Apps.
The affected flows are across multiple solutions, with some owned by my own account and others by a service account.
They worked fine yesterday, and my attention was drawn to this when a staff member sent me a screenshot stating they were unable to trigger one of the flows:
I tried modifying the flows in Dev and deploying with no change in behavior. I was able to successfully trigger the flows directly, and they did what they were supposed to do, but the slow run never populated in Power Apps. I created copies of a couple connected flows in the same solution and redeployed, the new flows work fine with hull run history in real time.
I have a couple child flows that are impacted by this that are called from several other parent flows, so I am hoping to find a way to restore the original flows to full working order to prevent having to remap all of the parent flows. I also want to know what causes this so I can avoid it in the future.
While trying to identify potential causes for this to happen today, I revisited what I was doing yesterday. I am working on transitioning sets of flows and dataflows from being owned by me to being owned by the service account, and was dealing with connection references in the process. All connection references on the affected flows showed valid, and different affected flows had different connection references in use, so I ruled that mostly out.
Any advice on things to check or try would be appreciated!
20
Share
Report
All responses (
Answers (
