Skip to main content
Question

Delay in Sub-Zap, no reason why

  • October 16, 2026
  • 1 reply
  • 15 views

Hi, recently I was getting some delayed status in a sub zap, the main zap gets triggered but once the sub zap started it took 15 min to go through the sub zap and return to the main zap, it happened twice (once it runs, the zap returned the value, so it was marked as completed after all), any idea what’s the problem? It hadn’t happened before. The recent runs are fine

1 reply

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • October 16, 2026

Hi ​@Vivacioustiger 

Help links for using Sub-Zaps: https://zapier.com/apps/sub-zap-by-zapier/integrations#help

 

Help link about Delayed Zap Run Status: https://help.zapier.com/hc/en-us/articles/20505304170637-Review-run-statuses-in-Zap-workflows#h_01K7PERCH9W2X4DNV0A9DBA17G

 

Data must be returned: A sub-Zap must return data. For example, if none of the paths are successful or data is filtered out before returning, the parent Zap run will remain in a Delayed state indefinitely.

  • If you find a parent Zap stuck in Delayed, open the sub-Zap run from that parent Zap and check whether the sub-Zap actually returned any data.
  • To prevent this, add a fallback path to your Sub-Zap. This ensures that if none of the other paths run, the fallback will run and return data to the parent Zap.