Skip to main content
Question

Multiple Orders - Overlapping issue

  • March 9, 2025
  • 6 replies
  • 53 views

  • Beginner
  • 2 replies

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?

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

6 replies

DavidLGS
Forum|alt.badge.img+6
  • Zapier Solution Partner
  • 209 replies
  • March 9, 2025

  • Author
  • Beginner
  • 2 replies
  • March 9, 2025

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


DavidLGS
Forum|alt.badge.img+6
  • Zapier Solution Partner
  • 209 replies
  • March 9, 2025

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. 


  • Author
  • Beginner
  • 2 replies
  • March 9, 2025

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

 


DavidLGS
Forum|alt.badge.img+6
  • Zapier Solution Partner
  • 209 replies
  • March 9, 2025

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. 


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 9751 replies
  • April 3, 2025

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! 🙂