Help! My Dataverse flow does not trigger anymore!

Today suddenly my flow does not trigger anymore. My flow should trigger when a new account is created but suddenly it doesn’t trigger my flow anymore.

Dataverse flow no trigger try catch
Dataverse flow no trigger try catch

First steps to debug the issue

First of all I tried to rerun a previous flow run. This flow still ran without any issue.

Dataverse flow no trigger flow runs history
Dataverse flow no trigger flow runs history

Then I clicked on the All runs to get to the Full Run history. Then within the Failed checks view I’m hoping to find a clue.

Failed checks dataverse flow no trigger
Failed checks dataverse flow no trigger

In the failed checks view I can see the flow that failed to trigger:

a flow does not trigger anymore see Failed checks
Help! My Dataverse flow does not trigger anymore! 1

And in the flow run details for this flow that failed to trigger, I got another clue.

Dataverse flow not trigger Flow failed first
Dataverse flow not trigger Flow failed first

What does this mean:

Entity ‘callbackregistration’ With Id = 5f079dee-9d84-ee11-8179-002248b1fb30 Does Not Exist

Well something does not exist.

Fixing the flow when a flow does not trigger anymore

dataverse flow no trigger Handler
dataverse flow no trigger Handler

So how do we go about fixing these flows that fail to trigger?

First step is to switch off the flow using the Turn Off option in the menu.

Then after that Turn the flow back On.

And that is it!

So what causes these kind of issues?

Understanding Power Automate flow schemas

When you run a flow there are a number of elements important to run a flow.

  • Connections (You can’t run actions without connections being valid!)
  • Input Parameters
  • Output Parameters

If any of the above change then you will find that testing a flow from a previous run will not work. But also if any of the above change in a child flow the parent flow will report issues. Restarting (Turn Off followed by Turn On) the parent flow may give you some error messages while you try to save the flow.

In our case we didn’t have input or output parameters in our flow. But we did have child flows that had their schema changed as some additional output parameters were added.

Regularly restarting your flows (in development only!) might be a good idea. So that you are at least aware of the issue before users report failures of the system.


Discover more from SharePains

Subscribe to get the latest posts sent to your email.

Avatar of Pieter Veenstra

Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There's a better way — and I can show you exactly what it looks like. I'm the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide. For over 30 years I've been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions. You can contact me using contact@sharepains.com

Related Posts

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Discover more from SharePains

Subscribe now to keep reading and get access to the full archive.

Continue reading