Skip to main content
Best answer

Created a new Zap and it stops on step 2 saying it is delayed but doesn't say why?

  • July 29, 2026
  • 4 replies
  • 23 views

Forum|alt.badge.img

 I build this validation zap that triggers on new/updated entries mapped to a table view.

 

When I kick it off for test it fires each time and then stops on #2 and says delayed.  There is no delay set and the #2 action simply sets the status field in that record as validating (new records default to new status)… then the rest of the zap is to run all the validations but it isn’t moving past #2.  Other than the zap has been delayed I can’t see why. HELP.

 

Is there another place I can get more detail on why it shows delayed?

Best answer by pdehaan

it seems the interface was incorrectly showing it was delaying on step 2 which was a simple table update and no delay but it appears it was on the step 3 process which was a sub zap that had a delay for queue in it.  I think it is the interface showing it was stopping at the step before is what was causing the issue and making no sense.  Thank you all.

4 replies

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

Hi ​@pdehaan 

For us to have true context, post screenshots showing how your Zap steps are outlined and configured.


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • July 30, 2026

Hi ​@pdehaan 👋

Are there any Delay actions in the Zap? Asking since usually it’ll show a status of “Delayed” on a Zap run if there’s a Delay action that still needs to finish running. You can learn more about run statuses here: Review run statuses in Zap workflows

But as Troy said, if you can share screenshots of the Zap’s set up that’ll help us to get more context on what else might be causing that delayed status. 


Forum|alt.badge.img
  • Author
  • Beginner
  • Answer
  • August 3, 2026

it seems the interface was incorrectly showing it was delaying on step 2 which was a simple table update and no delay but it appears it was on the step 3 process which was a sub zap that had a delay for queue in it.  I think it is the interface showing it was stopping at the step before is what was causing the issue and making no sense.  Thank you all.


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • August 10, 2026

Glad you tracked down what was causing it ​@pdehaan! 🎉 Thanks for coming back to share that it was the Delay step in the connected Sub-Zap that led to that Delayed status appearing. I've flagged this to our Product Team so they can look at making the cause of the delay clearer in cases like this.