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 a scenario where multiple Zaps call a sub-zap that does some data processing and calls QuickBooks Online “Create Sales Receipt” step. Sometimes the sub-zap fails on QBO step with the following error:

Too many Zaps trying to access the same resource at the same time. It will be retried after 15 seconds

The sub-zap logic eventually succeeds, however it fails with the error:

Did you fork or replay this step? We expected callbackUrl to be stored!

I assume that the callbackUrl gets lost during the retry due to the retry. Has anyone figured a way to work around this?

Same here — retry drops the callbackUrl, likely due to Zapier’s retry logic; splitting or delaying sub-zap calls helped in my case.

  • Faced same issue with sub-zap retries
  • Zapier drops callbackUrl on retry
  • Fixed by spacing out triggers (e.g., 10–15 sec delay)
  • Also split traffic into multiple smaller Zaps

Hi ​@stankovski! 👋

Just came across this and wanted to check how you’re getting on. Did iklionjon’s reply help you to get things solved?

If not, does the Zap have Paths with more than one Return from Sub-Zap action in the Zap?

If it does, then according to this help guide on Sub-Zaps, it’s expected that you’d see that error:

5b7aa48de5da28c436399c2fe98a0dd9.png

You’d need to ensure that the paths run are set to use sequential execution.

Keep us posted on how it’s going, want to make sure you’re all set! 🙂

Thanks ​@jiklionjon for sharing, I’m also trying to increase the delay before the requests to avoid these errors altogether. But I’m still curious what the right solution is for error handling.


Hi ​@SamB, thanks for the reply. I do have a fork in code that has 2 returns from sub zap. It’s a fork based on the error in the QBO action. If it fails I want to send an email and if it succeeds I exit the sub zap. Is the recommendation not to have a return from sub zap as part of the error flow?

Edit: just checked the link you have shared about sequential execution. Will give it a try. 

That’s great, ​@stankovski! Keep us posted on how it goes with sequential execution, fingers crossed it’ll sort it 🤞

OK, I can confirm that switching to sequential execution has resolved the issue. Thank you all for your help!

YAY!!! 🎉🎉🎉 You’re welcome, ​@stankovski! I’m so pleased switching to sequential execution did the trick. 😊

Do reach back out if you need help with anything else at all. Until then, happy Zapping! 😁⚡

Terms & ConditionsAccessibility statement