Invalid PrincipalId=00000000-0000-0000-0000-000000000000 Guid.Empty doesn't exist - Power Automate Trigger


The title just rolls right off the tongue doesn't it?

This was a strange one.  We had a flow which looked fine, but for some reason it would not trigger (dataverse row on add).

When going into the flow, it said there was a problem with the trigger and the following message appeared.

Invalid PrincipalId=00000000-0000-0000-0000-000000000000 Guid.Empty doesn't exist.

Well that sounds curious.

I did a bit of googling and nothing immediately of note came back.

Then I thought of callbackregistrations.  These are the records that are created that essentially are records of triggers for your flows.  Without one of these, the flow would not trigger, with two of these it might trigger twice.

You shouldn't have to interact with callbackregistrations, but sometimes it is necessary.

I used the dataverse web api as described in this blog post to look for any registrations:

https://community.dynamics.com/blogs/post/?postid=a8d821b1-5428-4a59-8a24-f0ad7523775f

I found a registration.  My initial thought was that this may have been created a long time ago and maybe the developer account is not longer on our system.  Whilst the flow has had its owner changed, maybe the callbackregistration needed some help.

I used Power Automate to delete specific registration as described on this blog post:

https://rajeevpentyala.com/2021/01/30/callback-registration-expander-system-jobs-waiting-for-resources/

Then turned off the flow and turned it back on and hey presto, a new callbackregistration and the flow began to trigger correctly.

Hoping this helps someone or at least reminds me in years to come!



Comments

Popular posts from this blog

Assigning Windows 10/11 Enterprise Subscription Activation Licences to Hybrid Azure AD Joined Devices

Power Automate: Get first item in output

De-selectable radio buttons - Power Apps