Flow Not Triggering When Dataverse Condition is Met

[kellykirk]

The general problem first, then deeper background: I can't figure out what's causing some of the contacts in my CRM to be "invisible" to a flow despite the CRM registering the change in the trigger field.

More details:

I have a flow that's triggered when an MS Dataverse row is added or modified. The trigger is the field for a score from our marketing platform:

The flow has been running consistently for the last two weeks with no failures or errors:

I found out earlier this week that about 2,000 contacts haven't had their score updated this week despite their score increasing because they never triggered the flow.

I checked the audit history for about 50 records and they all record the row/field update in the database:

After a LOT of digging, I've discovered that this seems to trace back to a field mapping change made back in April, so I think this is what's causing the problem, but I'm not sure how. Initially, the mapping was (CRM) HubSpot Score = (HubSpot) HubSpot Score, but now it's (CRM) HubSpot Score = (HubSpot) Lifetime HubSpot Score.

It seems that anyone that had a score change (even if the score was just 0) during that switch is no longer triggering the flow that adds a date stamp when the score increases:

I can't figure out what's causing these contacts to be "invisible" to the flow despite the CRM registering the change in score and I'm hoping someone here has a suggestion.

And, yes, I've checked and the flow is set to trigger the correct field.

[Matthy79]

Hello @kellykirk 

Have you checked the flow if it is set to trigger for the correct field? Just kidding 😉

These triggers can sometimes be very annoying. Everything is setup correctly and it is still not working. Have you tried to delete the trigger step and add it once again (because you said a field has been changed/added). Problem with this is, that you will lose the dynamic content in the steps following.

But you could test it another way. Create a new flow adding the same step and a compose action saying “I was triggered”. If this new flow fires you will have the confirmation that the trigger in your first flow has to be created again.

[LinnZawWin]

Hi @kellykirk 

Can you try to check the filteringattributes column of your flow in the callbackregistration table to see if something seems off?

The easiest way is to use SQL 4 CDS tool in XrmToolBox.

select WF.name, entityname, filteringattributes from callbackregistration CB
INNER JOIN workflow WF ON workflowid = CB.name
WHERE entityname = 'contact'

[kellykirk]

I have XRM Toolbox for some other  CRM processes, but I have zero knowledge of SQL so I'm not sure what that's supposed to do. I copied that formula and just got a massive error. Did you use some filler text that I should be replacing with my own information?

[LinnZawWin]

@kellykirk 

I guess some of the callback names are not GUID. I have updated the filter to check the length = 36. Can you try again?

The only dynamic filler text is 'contact' which should be the same for your case since your flow is triggering on the Contacts table based on the screenshot.

select CB.name, WF.name, entityname, filteringattributes from callbackregistration CB
LEFT JOIN workflow WF ON workflowid = CB.name AND LEN(CB.name) = 36
WHERE entityname = 'contact'

[kellykirk]

This was my next step if I couldn't figure anything else out, so I went ahead and did it. I removed the trigger, but before I did that, I took screenshots and documented *every* part of the flow to make sure I set it back exactly the same once I readded the trigger.

Now the entire flow is broken.

An expression that's been running like clockwork is now saying it's invalid and getting a result of "null," which shouldn't be the case, because when I check the JSON in the trigger, the exact info needed to run the expression is there. 

I'm working with some peers and we've determined that there's a simpler way of doing this in the originating "score increase" platform of HubSpot. It's a 2-step workflow with no branch logic or expressions needed.

Then we're just going to map that date-stamped field to our CRM instead of trying to fix this fragile Power Automate flow that continually breaks because of the complex branch logic and expressions involved in getting it to time-stamp a field.