Suggested by Nitesh Sharma – New
Dear Microsoft Team,
We would like to kindly request the implementation of a feature within the Dataverse platform that notifies users when a Power Automate flow fails to trigger, despite changes occurring in the underlying data.
Recently, we encountered an issue where certain flows did not trigger even though new records were created or updates were made in Dataverse. This lack of triggering resulted in delays and challenges in our automated processes, as we were not immediately aware that the flows had not executed as expected.
A built-in mechanism to alert users when a flow does not trigger—despite relevant data changes—would greatly enhance visibility and allow for quicker troubleshooting, thereby improving overall reliability and operational efficiency.
How can a user know that the flow is not triggered by the Microsoft backend due to failed callback registrations?
We appreciate your consideration of this request and look forward to any updates regarding its feasibility.
Thanks