Skip to main content
Question

Issue with Jumbled Request Order in Zapier Despite Correct Order from My System


Hi,

I’m encountering an issue with the way requests are being processed in my Zap. Specifically, I’m syncing recurring booking data (e.g., bookings B1, B2, B3, B4, B5) from my system via a Webhook trigger in Zapier. While I’m sending the requests to Zapier in the correct order, I’ve noticed that the order of these bookings is getting jumbled up in the Zapier history and when syncing data to Google Sheets.

I’ve already tried adding a time delay between requests and using Zapier's Delay action, but the order is still not maintained during processing. The requests are being processed asynchronously, and it seems that Zapier is not respecting the order in which they were received.

Could you please assist me with:

  1. Ensuring that the requests are processed sequentially, respecting the order in which they were sent to Zapier.
  2. If there are any configuration settings or best practices that can help maintain the order of requests when processing large batches or recurring data.

Additionally, I would appreciate any suggestions or recommendations for handling this issue, especially when dealing with multiple booking data points sent in a batch.

Thank you for your assistance!

Did this topic help you find an answer to your question?

2 replies

Troy Tessalone
Forum|alt.badge.img+14

Hi ​@Sahildeep 

For us to have more context, post screenshots of your Zap Runs history as proof.


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 7304 replies
  • February 13, 2025

Hi there ​@Sahildeep! 👋

It’s been a while since you posted here, were you able to find a solution?

Webhooks are usually processed as they arrive, but the order is not guaranteed, especially if multiple webhooks are sent in quick succession. The Delay After Queue action would space out each run, but it doesn’t ensure they run sequentially if they were queued in the wrong order.

I’m assuming you’re using the Catch Hook trigger, right? If so, I wonder if you might have better luck switching to the Retrieve Poll trigger instead. 🤔 Polling triggers check for new data every 1-15 minutes (depending on your Zapier plan) and typically process records from oldest to newest. Thinking that may help to ensure that the bookings are handled in the correct order. 

If you have any success with the Retrieve Poll trigger or find another solution, let us know—we’d love to hear from you! 🙂