You’re offline. This is a read only version of the page.
Hi all!
We have an issue with power automate.
There are a few automated flows added to a solution, most of them get triggered when a new record is created or modified in power apps, so the flows are using dataverse trigger.
All flows have been working as expected, however today we noticed that some of the flows stopped working - meaning that there is no indication that the flow even got triggered/attempted to run.
We haven’t been able to identify why those flows are not working properly, tried everything, from turning off other flows with similar triggers to deleting and adding new trigger on the flow, turning flow off and on again… from all the testing today, it only got triggered a few times and there is no indication why other times it doesn’t get triggered.
Has anyone faced with similar issue and managed to find a cause and a fix?
This has also happened to me several times. I have hundreds of triggered flows running within the business. The fact that I can't rely on them working without constantly monitoring if they're working or not makes this product literally useless.
It's a fun idea Microsoft, but your execution is exactly what is expected of such an incompetant company.
I have seen this same disconnect between Power Automate and Dataverse. Often the only way we can 'fix' the trigger failure is to delete the action step and create a new action step. Theoretically this creates a new webhook. It has only happened intermittently, but it's happened a few times across different tenants.
Has anyone been able to establish a set of reproduction steps to reliably provoke this disconnect?
Are you aware of any update?
I think I'm having the same issue: the Dataverse trigger for modifying a row. I've tried the turning off/on and also, switching the trigger from 'modify' to 'modify and delete' and 'add and modify', but am not able to trigger the flow.
Also sharing this comment/solution: it did not work for me, but may for others
https://simondoy.com/2023/06/07/issue-when-changing-power-automate-dataverse-table-triggers/
Hi, I had the same problem. I logged a ticket with Microsoft and they dug into it and found that there is a known issue which is causing the dataverse trigger to stop working intermittently. They are working on it but it is not shown anywhere as an issue. No ETA was provided.
My only work around is to turn off and turn on again, or edit flow and run test, then create/update a record to trigger it. This will work for a while but will stop working again in an unpredictable amount of time.
This is a recent issue, and may not be related to yours, but if anyone else stumbles upon this, I hope this is of use.
Hi!
Have you managed to figure out what was the issue? I have the same problem, when one flow suddenly stopped triggering on create
@AhmedSalih I have admin permissions so was able to check just now that there are no DPLs added. As for the user licence, the flow owner has licences, though not sure if there is a particular licence needed? But some of the other dataverse flows seems to trigger so I would imagine licence shouldn’t be an issue too.
@icetea you Power Platform Admin or IT should be able to check that for you. For the Flow owner, in the Power Automate Details Page, see who is the owner of the flow and make sure your Admins check if they have a premium license. For the DLP, it is in the Admin Center of the Power Platform.
Regards,
Ahmed
If my reply helped you, please give a đź‘Ť. And if it has solved your issue, please consider a đź‘Ť & Accepting it as the Solution to help other members of the community find it more.
My Blog: www.powerplatformplace.com
Hi @AhmedSalih
Thanks for your advice! I’m not entirely sure where I can check these, any idea?
Thanks!
#1
WarrenBelz
791
Most Valuable Professional
#2
MS.Ragavendar
410
#3
mmbr1606
275
Super User 2025 Season 2
Share
Report
All responses (
Answers (