Skip to main content

I created a Zap that finds duplicates in Zapier tables after new records are added and then (intended to) update a field with “duplicate” once duplicates are found. Everything is seemingly connected/working...but as the Zap runs it ONLY updates the “new” record and not the “old” record in Zapier tables that it has also found as a duplicate.

How do I get the Zap to update BOTH of the duplicative records that were returned with record locators?

Pictures below for key steps/activities:

 

 

 

@ashland 

Make sure you test live with the Zap turned ON, then review 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/

Help links for using Looping: https://zapier.com/apps/looping/integrations#help

 

  • When you test this action, the Zap will only create the first loop.
    • It will not create any other loops during the test.

 

 


Great advice - for some reason the Zap isn’t triggering when I check the run history (which is why it works during the build/test but not with real data). It seems to be set up correctly: 

 

 

 

 

(And when I click on “Open in Tables” it opens the correct Table….and tests go through). It DOES work/trigger when I manually add a row with the data (so it doesn’t seem to be my Zap set up). But it does NOT work when I import data into the Zapier Table. Is there a known bug with importing data that is supposed to trigger “new or updated records” zaps? Or what is the trigger set for importing data if it isn’t new or updated records?


Reply