Sub-Zap delayed and never completes

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/

I have the same problem. I’ve had a workflow that executed just fine, calling a sub-zap without any issues. As of two days ago all the calls to the sub-zap are not marked as “Delayed”.