Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

I have Zapier Tables.  Most of my ZAPS trigger from a new record created and they are triggering from VIEW Tables or a Table that has been filtered from the Main Table  

 

Let's me give you the steps

 

1) I create a record in JotForm

2) Jotform connects to a Table and creates a record in the Main Table (we will call this Table 1)

3) At this point there is only 1 record in the Main Table (Table 1)

3) The Main Table (Table 1) is filtered to create a View Table; the Zap then triggers from the View Table

4) The ZAP is triggered and runs, and the purpose of the ZAP is to create a NEW Record in second Table (we will call this Table 2)

5) The ZAP should create only 1 new record in Table 2 but instead it is creating 2 records in Table 2

 

How do I know that it is an issue with the View Table (from Table 1)?

 

If I have the ZAP trigger from the Main Table (Table 1) instead of the View Table (or sub stable to Table 1) and then filter by the same filter I used to create the View Table (or sub table to Table 1), I will only get 1 record created by the ZAP

 

THIS IS OCCURRING ACROSS MULTIPLE ZAPS THAT ARE TRIGGERING FROM THE VIEW TABLES OF MULTIPLE MAIN TABLES

 

And it seemed to start about 24 hours ago….it is a bit messy!

 

Hi ​@blueguy,

 

Welcome to the Community.

If Zapier Tables creates duplicate records when triggering from a View Table, it could be a setup issue. Check the task History to identify where duplication occurs, recreate the Zap with careful field mapping, or create a new View Table and Zap to isolate the issue.

 

I hope this helps. If you have any other questions, don't hesitate to ask.
 

 

 

 

 

Here are more details…

 

Okay....here one example and there are others

 

I am triggering a ZAP from a Table and the end result is that the ZAP does not run twice, but duplicates the result twice.

 

The Table is called Master Follow Up Note (Medical); the ZAP triggers from a subtable (view Table) called View:99213

 

Here is the entry in that View Table:

 

image.png

 

Note there is only 1 entry.

 

The ZAP that runs is called: Follow up note (99213) pathway {to Holding Pen}

 

I have highlighted the ZAP that ran and it ran only one time:

 

image.png

 

I have highlighted the actual ZAP run here and it is perfect:

 

image.png

 

YET, THE RESULT OF THE ZAP RUN IN THE GOOGLE SHEET (THE LAST STEP) IS THAT 2 ROWS ARE PRODUCED:

 

image.png

 

only 1 row should have been produced but as you can see there are 2 entries and they are the same

 

FURTHERMORE, OTHER ZAPS ARE TRIGGERING FROM THIS PROCESS EVEN THOUGH THEY SHOULD NOT

 

Take a look at this ZAP, which ran: New Injection Orders from FU Note

 

This ZAP triggers on the same Main Table but on a different view; this ZAP triggers on View: New Injection Table

 

image.png

 

Going to that View or Subtable called New Injection Table, you can see that there is no entry for this ZAP to Trigger yet it did Trigger and run as I have shown you above

 

image.png

 

This ZAP's (New Injection Orders from FU Note) final result is to send a single email.  HOWEVER, THE ZAP SENT 3 EMAILS TO MY INBOX (please note the time).

image.png

 

Looking at the ZAP history of the New Injection Orders from FU Note we can see that only 1 ZAP run triggered but 3 emails were sent; FURTHERMORE, THIS ZAP SHOULD HAVE NEVER TRIGGERED IN THE FIRST PLACE (AS THERE WAS NO TRIGGER ROW IN THE View: New Injection Table)

 

image.png

 

IN THE END, WE HAVE MULTIPLE ZAPS TRIGGERING FROM A TABLE AND ITS SUBTABLES (VIEWS); ONLY 1 ZAP SHOULD BE TRIGGERING YET MULTIPLE ZAPS ARE TRIGGERING (DESPITE THE LACK OF A TRIGGER ROW); WHEN THE ZAPS DO TRIGGER THEY ARE PRODUCING MULTIPLE RESULTS.

 

 

Hi there, ​@blueguy 👋

Thanks so much for sharing those details here. It looks like the images haven’t uploaded fully so we can’t see those examples. That said, I can see that you also reached out to our Support team about this and they’ve escalated the issue to our engineering team. We can’t provide any sort of ETA on when it will be resolved but they’ll be in touch via email with any updates on that. 

If you have any further questions regarding this it would be best to continue the existing email conversation with the Support team. Please do keep us in the loop on how you get on with this though—keen to ensure this gets sorted! 🙂

You said: “We can’t provide any sort of ETA on when it will be resolved but they’ll be in touch via email with any updates on that. “

I get that there are often issues that spring up.  Our business is quite dependent upon your services and products, and yet, our business does not stop either.  If you told me or if someone could reach out to me and say, “We think we can have this fixed in 3 days”, then I might tough it out for 3 days.  But if you told me, “I don’t know or this is going to take 3 weeks”, then I would look for another solution.

I am trying to figure out what to do next….

 

Got it?

 

gml

Really appreciate your candor here, ​@blueguy. I completely understand how hard it is to plan without a clear timeline and really wish we could provide an estimate for when it’s likely to be resolved by. Please know that the team is actively working on it and they’ll email you with any updates as soon as they have them.

As a workaround, the Support team had suggested changing the Create Spreadsheet Row action with a Lookup Spreadsheet Row action which has the ability to create a new row if an existing one is not found. And to add a Delay After Queue action to help prevent duplicate rows from being created. I’m not able to see into the Zaps on your account but wanted to add that if there’s other actions of your Zaps that shouldn’t run if an existing row is found then I’d suggest adding a Filter as well. The filter could be set up to check that the _zap_search_was_found_status field from the Lookup Spreadsheet Row action is false. This will ensure that the Zap only carries out those actions when a new row is added to the spreadsheet. 

Thanks so much for your patience on this and I’m sorry for the uncertainty caused. Please do let me know if there’s anything else I can help with in the meantime.

Reply


Terms & Conditions