Solved! Go to Solution.
@Anonymous @RSawyer Cannot thank you enough!!
Seriously MS needs to get on track with this. I can see more and more posts pop-up online in regards to the issue with no clear solution, apart from yours!
Describing step by step in case we manage to help someone out there:
1. Located all the steps in my Automate that included SharePoint somehow Create Item (SharePoint) and Update File Properties (SharePoint)
2. Created an exact duplicate underneath those in step 1
3. Went to my PowerApp
4. removed the Automate flow (& always take a copy of the code )
5. re-added the Automate flow and worked.
Let's hope your flow does not have many SharePoint action steps as it will take some time!
I agree with the prevailing opinions on this forum.
This error is UNACCEPTABLE, and Microsoft need to fix it quickly.
The worst issue with "Trigger Errors" with a flow is that there is ZERO error detection connected to it.
So basically, your PowerApp can call the Flow, but if the flow did not even TRIGGER, there's no record of a failed flow run, and PowerApps actually thinks that the flow was successful. Obviously, this is absurd, as there should be a record somewhere that the flow was attempted to be triggered.
I have a PowerApps triggered flow for uploading documents to a SharePoint Document Library - this is used to upload all the important manufacture information for a clients orders. This morning, I discovered that this Flow actually stopped working about 48 hours ago, and so approximately 100 files were not uploaded, but without any warning or error given, or even a record of the attempt, so I don't even know which 100 files failed to upload. As many of these files have been deleted from the Users personal computers (trusting that SharePoint would store them correctly), we are now missing up to 100 files relating to Customer Orders. We are now going to miss these Order delivery dates, and suffer financial penalties as a result - Who do we talk to in Microsoft about putting in a Claim for these funds, as it was clearly caused by a Microsoft Technical issue?
There is also no global or central warning that a Flow has a Trigger Error (which, as we have all discussed and discovered, can materialise in a working flow for absolutely no reason, or more probably, a behind-the-scenes update that Microsoft pushes out without any warning, release notes, or apparently, sufficient testing).
The only way to know if a Flow has a trigger error is to go into the details of each one.
So right now, I now have to perform a DAILY task where I go into EVERY flow I have created (across multiple tenancies) in order to make sure that Microsoft hasn't broken them in the past 24 hours. - this task now takes up half of my day, EVERY day, thus HALVING the time a can work for my clients.
Who do I speak to in Microsoft about putting in a Claim for all my "Lost business" due to this Microsoft Technical issue?
Can we please have some sort of indication that Microsoft at least acknowledge the issue, as well as an indication when the random trigger errors will be fixed. We also need an indication of when there will be better error detection of flows with Trigger Errors, and when Flow will correctly report to PowerApps that the Flow did in fact NOT run.
Without assurance that these issues will be fixed, I cannot have any confidence in using Microsoft Flow for ANY automated process, and will have to advise my Clients that Microsoft is too unreliable to use Flow in production systems.
I have worked out a quicker way to resolve issue, which I have passed onto Microsoft support this morning. I would recommend you take a backup of your Flow before proceeding.
Rather than having to edit the flow and fix every step that has a connection, the quick fix is to load the connection screen for the Flow. Remove every connection (by clicking the "x"). Save the Flow and connections are added back in automatically.
From what I can see the steps are not affected. Reconnect the Flow from PowerApps and you should be good to go.
I have been advised by Microsoft support to raise an idea. This will then be escalated internally, please use the link to up vote and add comments.
Hi all, thanks for this I have been tearing my hair out trying to work out why it doesn't work for a seemingly random set of users. Hopefully this will be the solution.
Quick tip that might be helpful though. I too have been frustrated by the lack of an error message when the flow didn't run, both in app and in power automate.
You can solve this by adding a respond to PowerApps action right after your trigger. That way you get fast confirmation that the flow has started and can notify the user if there is a problem.
Hi Nicknee, for me this turned out to be a company wide user permission that had to be changed. (Apologies I cannot remember the name of the setting)
I had to have a call with Microsoft and my org admins to resolve it. If nothing else posted here has worked raise the issue with your IT support and get them to push it to Microsoft if they cannot fix it.
Explore the latest innovations, learn from product experts and partners, level up your skillset, and create connections from around the world.
Your chance to join an engaging competition of Power Platform enthusiasts.