Hi @febbyrg 

Check your Zap Runs history details to see the DATA IN/OUT for each step to help you trace the data flow and troubleshoot: https://zapier.com/app/history/

We would need to see specific examples with screenshots from the Zap Runs with info showing the claim about the Zap still triggering for other Contact field changes.

Hi @Troy Tessalone,

Thank you for your reply.
I'm sorry for not getting back to you sooner.

Please find screenshots of two examples below from the history of Zap Runs (Data In/Out).
I appreciate your help.

Example 1:

Example 2:

@febbyrg 

From the screenshots we can’t definitely tell as those are 2 separate examples with different email addresses.

Hi @febbyrg! 

Not sure if you’ve since managed to get things solved but it looks like the Zap is using an older version of the Microsoft Dynamics 365 CRM app as I’m seeing a version number in the app title here:

Can you try upgrading to the latest version and let us know whether that helps to get it triggering as expected? 

Hi @SamB,

Thank you for your reply.
I checked there is no new version available for the Zap App Microsoft Dynamic 365 CRM (attached screenshot).

Can you please help where I can find the version history of the MS Dynamic Zap App?
Thank you!

 

Thanks for getting back to me @febbyrg. 

There isn’t any public-facing version history that I could share a link to but, from your latest screenshot it looks as though the Zap may have since been updated as there’s no version number shown on the trigger step. So that side of things appears to be sorted! 

With the Updated Contact trigger you can select a field to monitor for changes but you can’t select a specific value that the field needs to contain in order for it to be triggered. There appears to be a note on the Updated Contact trigger that may help to shed some light on why the Zap is triggering unexpectedly here:

I did some further digging and found a bug report that was closed recently for an issue where the updated contacts trigger was running for updates to fields other than the ones selected in the trigger. For those cases it appears that the issue was caused by bulk updates being carried out in Microsoft Dynamics. 

The bulk updates changed the modified dates on multiple contacts when they were updated. The way it works is that the Updated Contact trigger initially sorts records by the most recent modified date, and then creates a unique id with the current value of the "watched" fields (in your case the Membership Status field). As the modified date was updated for contacts that the Zap hadn’t seen before, it considered them to be a new updated contact that needed to be triggered on. Which confirms what was mentioned in the note. See Why are old items triggering my Zap? guide for more details on why this sort of thing can happen.

Do you think that might be what’s happening in your case as well?

If so, I wonder if it might be worth adding a tag or label to certain contacts that you want to have trigger the Zap, then use a Filter to check that this tab/label is present, or set it to only continue if the membership status matches a certain value, so that the Zap only continues for specific updates. 

Looking forward to hearing from you on this!

Hi @febbyrg 

Just wanted to circle back in here to check how you’re getting on. Was it a bulk update that was the cause of the issue? And did adding a filter help to ensure the Zap only continued for the correct contacts?

Keen to ensure you’re all set so please keep us updated on how you’re getting on!

Hi @SamB,

I apologize for the late reply.
And thank you for following up.

Let me ask the team how they update the data.
We did add the Zapier filter in the middle of the process, but it still counts as one Zap process.
Our goal is also to minimize the zap process, with specific updated fields in the MS Dynamic.

Thank you!
 

No worries, @febbyrg! 

Let me ask the team how they update the data.

Sounds good, we’ll wait to hear from you on that then.

We did add the Zapier filter in the middle of the process, but it still counts as one Zap process.
Our goal is also to minimize the zap process, with specific updated fields in the MS Dynamic.

When you say “minimize the zap process” are you referring to reducing the tasks used by the Zap? If so, it may help to know that any actions carried out by a filter do not count towards your Zap’s task usage. See What does not count toward task usage? for more details. Hope that helps!