@Mitchell Zezima 

Probably.

When in doubt, test it out.

@Mitchell Zezima 

Yeah sounds like you are encountering race conditions.

It seems to be a timing issue, the next Zap that is triggered is trying to read from the spreadsheet seconds after the previous Zap has created the new row and just returning “false”.

If I test the zap step using the same uuid that im using it will return true, but because they are running so close to each other its not got enough time to actually read the new row so returns false every time.

Thank you 

@Mitchell Zezima 

Can you post a screenshot with how your Zap step is configured?

If the Zaps are all processing at the same time, then none with find the search value, unless it already exists.

Another option to try instead of GSheets is Airtable as the lookup table.

Hi Troy,

I initially raised the issue with them when I originally created this post many months ago, and still haven’t had a response. So unfortunately I’m on my own when it comes to resolving this as Servicem8 just don’t care. 
 

The proposed workaround does not involve Servicem8 but instead uses google sheets as you obviously know so a fix should in theory be possible because of this. I just don’t understand why the lookup/create row step is returning false when there is in fact a row which contains the uuid when I manually search for it in the sheet. This is an issue with Zapier/sheets rather than servicem8 right? 

@Mitchell Zezima 

You may want to try reaching out to ServiceM8 Support, who likely created and manages their Zap app integration, about their Zap webhook trigger issue where it fires multiple times.

Otherwise, you may want to look into using a different approach for the Zap trigger.

Possibly using the ServiceM8 API: https://developer.servicem8.com/reference/get-formresponse-all

Apologies I provided incorrect screenshots on Zap run 3. This was a seperate Zap trigger, I will amend them now to the correct ones. Heres how the filter is set up anyway

@Mitchell Zezima 

Looks like the data were the same for Zap Runs 1&2 but different for Zap Run 3, which would help explain some of this.

Can you show a screenshot with how your Zap Filter step is configured?

@Mitchell Zezima

Try changing the Queue title, as per the field description which has a max of 32 characters.

 

 

Hi Troy,

Still getting the same error unfortunately 

Zap Run 1 

Zap Run 2 

Zap Run 3

Thanks

@Mitchell Zezima

Try changing the Queue title, as per the field description which has a max of 32 characters.

 Here we go in order

Zap Run 1 

Zap Run 2 

Zap Run 3 

Regards

@Mitchell Zezima 

We would need to see updated screenshots for the Zap Runs DATA IN/OUT.

Unfortunately not :( 

pictures here

@Mitchell Zezima

You need to add a Queue Title

 

Hi Troy, thanks will do. Do you think this is what has been causing the issue?

@Mitchell Zezima 

You need to add a Queue Title

Hi Troy,

Please see attached

Regards

@Mitchell Zezima 

Can you post screenshots with how your Delay step is configured?

Doesn’t look like your Delay step has been configured as Delay After Queue.

That is because the Zap Runs only show 2 inputs, rather than 3.

Zap Run 1  

Zap Run 2 

Zap Run 3 

Hi Troy see attached in order of runs (first run at the top). Hope this is easy to understand

Regards

@Mitchell Zezima 

Can you show screenshots of the DATA IN/OUT for the first 4 steps from each Zap Run?

Make sure to include the timestamps for each Zap step.

Hi Troy,

I have tried changing it to Delay After Que as suggested howver im still getting the same issue. Oddly enough one Zap triggered 3 times.

Heres the screenshots

Thanks Troy, will try this out I have now changed them all to “After Que”

@Mitchell Zezima 

If the Zap is triggering twice, then that’s due to the ServiceM8.

Try changing the Delay in Step 2 from a FOR to a AFTER QUEUE.

Re attached - thanks