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.

All of a sudden, Zaps that are calling a sub-zap just go into a delayed state and never finish.  The sub-zap doesn’t have any delay steps.  This was working fine yesterday for all the Zaps that call the sub-zap, but suddenly it stopped working and I can’t figure out how to resolve this.  

 

Hey ​@Nussbapj,

Is it for all the Sub zaps or this specific one? In the Sub zap, is it correctly catching the Return from a Sub zap? Also depends on the sub zap is being configured. Here is an helpful article about delay here - https://help.zapier.com/hc/en-us/articles/8496061204621-Common-Problems-with-Delay.

Referencing the details from the Subzap limitation article(https://help.zapier.com/hc/en-us/articles/32283713627533-Understanding-Sub-Zaps)-

  • Sub-Zap requirements: All Sub-Zaps must use the Start a Sub-Zap trigger and have a Return from a Sub-Zap action as its last step. 
    • All Paths branches must have a return from Sub-Zap step.
  • Task usage: Sub-Zap steps do not use any tasks.
  • Looping: You cannot use a loop step within a Sub-Zap.
  • Paths: 
    • If you use a Return from Sub-Zap step in more than one path branch, only the first one to match will run. Ensure your path branch logic is set so that only one path runs at a time. 
    • If more than one path branch runs and both contain a Return from Sub-Zap step, you’ll see the error  “Did you fork or replay this step? We expected callbackUrl to be stored!”.
       

As you also said, it was working well before it may be some edge case scenario or some temporary error that you are encountering. Hope it helps!

Hi ​@Nussbapj 

When a Zap calls a Sub-Zap it will be Status = Delay, since the Sub-Zap needs time to trigger and finish processing.

If the Zap is being stuck in Status = Delay, then that may indicate an issue with the Sub-Zap processing and returning a value (Zap action: Sub-Zap - Return from a Sub-Zap).

Check your Zap Run history details to see the DATA IN/OUT for each step in the Sub-Zap to help you trace the data flow and troubleshoot: https://zapier.com/app/history/

Reply


Terms & Conditions