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.

Issue Explanation

My current Zap is structured as follows:

  1. WooCommerce Order Trigger
  2. Filter Conditions
  3. Filter Conditions
  4. Google Sheets Update Row (x4)
  5. Google Drive Find a File
  6. Send Email

Problem:

If multiple customers place orders at the same time, Zapier runs all instances of the Zap concurrently. This can cause Google Sheets to update  rows due to overlapping executions, leading to mismatched data between customer’s inputs.

what can i do to be sure that each customer receives file with their input data/information being in sheets and not mixed with other orders/customer’s inputs?

Delay after queue

I have applied delay after queue after first step. title > unique order id , but results are same. What am I doing wrong

When you say the Google sheet gets updated 4x, is all that data coming in on a single trigger or is it somehow triggering the zap 4 separate times?

 

Hopefully it’s all coming in on the same trigger. If so, did you delay the queue long enough so that all the steps are executed before the next one is released?

 

You can do a timing analysis on the run histories to see when one trigger started, when it finished executed, then look at the queue step of “the next” trigger to make sure it was released after the first run is completely over. 

I appreciate your help, can you check screenshots? I have attached zap steps.

 

You’d have to look at 2 different run histories separately that are causing the conflict and see when one ends and the other starts as previously described. 

Hi ​@GNK, just checking in—were you able to get this sorted by increasing the delay in that Delay After Queue action? 

Let us know if you still need any help! 🙂

Terms & Conditions