Zap actions running in wrong order

Hi ​@cbeene 

From your screenshots, we can’t tell if these Zap step timestamps are from the same Looping iteration Zap Run.

There might have been a temp error/issue processing Zap step 12 in the Zap Run, which was then retried soon after if you have Autoreplay enabled.

If following Zap steps are NOT dependent upon a previous Zap step, then those Zap steps will attempt to be processed.

This may result in Zap steps with timestamps that appear to have processed out of order.

If you only want Zap steps to process after the success processing of a previous Zap step, then add a Filter step to check for an output variable from a Zap step that indicates the Zap step processed successfully.

Good day ​@Troy Tessalone  and thanks for the feedback. 

1. Yes, all of the screenshot and timestamps are from one loop iteration.  
2. We do NOT have auto-Replay enabled.  
3. If I add a filter before the Call Sub-Zap step, as you mentioned, don’t I run the risk of the step NOT being executed if the Call Sub-Zap action starts before my Create Record step, as did occur above?.  

​@cbeene 

Zap steps process in order.

Zap steps can be retried at later time if there was a temp error/issue with the Zap step processing, depending on the Zap step configuration settings and Autoreplay settings.

TIP: If you replay a Zap Run, then you can watch Zap Runs replay live to see how the Zap steps process to have more insight.

Help: https://help.zapier.com/hc/en-us/articles/8496241726989-Replay-Zap-runs

As an example…

Say you put a Filter step between Zap Steps 12-13.

Say that Filter step checks for an output variable value from Step 12 that indicates Step 12 processed successfully.

That mean Step 13 will only process if Zap step 12 processed in a way that passes the Filter step. 

Hey ​@cbeene,

If the Zap is running is expected, then it might be some issue with timpstamp happening in Zapier. But if you think it’s a bug, you can contact the Zapier support here- https://zapier.com/app/get-help. Hope it helps!

Thanks for the feedback ​@Troy Tessalone  and ​@Sparsh from Automation Jinn.  There is a piece of data from earlier in the process that step 12 and step 16 both use.  I opted to get the data for step 16 from step 12, to make sure 16 didn't run until 12 completed.