Skip to main content
Question

How to debug? Sub-zap sometimes ends up in "Waiting (delayed) state" - never completes


bridgman

I discovered that some of my zaps are going into a sub-zap black hole. I didn’t have a fallback path, thinking I had covered all options, but apparently not. Or maybe it’s something else?

How best to debug this? The sub-zap run history shows only successes. Looking in the data in the main zap doesn’t show anything glaring.

I did add a fallback path to hopefully prevent getting stuck, but I need to figure out what bad data is getting passed in that shouldn’t be.

 

 

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

2 replies

Troy Tessalone
Forum|alt.badge.img+14

Hi ​@bridgman 

For us to have more info, post these screenshots:

  • how your Sub-Zap step 3 in the parent Zap is configured in EDIT mode with the field mappings visible
  • how your Sub-Zap steps are configured in EDIT mode with the field mappings visible

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

Hi there, ​@bridgman 👋

Just came across this and wanted to check in—were you able to figure out what was causing the Sub-Zaps to get delayed?

If so, would you be open to sharing the solution? It could be really useful for anyone facing similar issues. 🙏

If not, could you share some screenshots of the Sub-Zap’s setup, as Troy mentioned? That should give us a bit more context to help troubleshoot. Make sure to blur or remove all personal information (names, emails, addresses etc.) from screenshots before sharing - you can use a tool like Zappy for that.

Looking forward to hearing from you!