Power Automate automated cloud flow (Dataverse 'When a row is added or modified' trigger) imported via managed solution shows status On but never fires in one environment (zero run history), while the identical flow works fine in two other environments. Connection reference, owner, and plugin registration all match. What causes a Dataverse trigger to not register/fire in a specific environment after import?
Screenshot 2026-0...
Screenshot 2026-0...
Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.
Since the flow works correctly in two environments but never fires in one—and there is no run history at all—the most likely cause is that the Dataverse trigger
registration/subscription was not successfully established during solution import.
Start by toggling the flow off/on, validating the connection reference, and creating a simple test flow against the same table.
If the test flow also fails to trigger, the problem is almost certainly environment-specific. At that point, review the environment's Dataverse health and,
if necessary, open a Microsoft Support case, as they can verify the backend trigger subscription and repair it if it failed to register.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.