For some reason, sometimes this Zap triggers twice for same email. So we added a filter. We store a key in storage and if its value is 1, then we skip that otherwise continue and set the value of key to 1 so next time its skipped.
In Zap history runs, it shows that filter successfully skipped second run, but in Gmail we are still receiving same AI generated email twice. Why could this possibly happening?
Any pointers would be helpful!
+5Hello
If the Filter shows it skipped but Gmail still sends twice, a few common causes:
Two runs fire at nearly the same time. Both can pass the Storage check before the key is written. Adding a short Delay After Queue before checking Storage can help serialize runs.
Another Zap with the same Gmail step is turned on. Double check there is not a duplicate or older version live.
The trigger is firing twice. Review the two Task History runs and confirm whether the trigger data is identical.
The Storage key is slightly different between runs or using a different Storage connection.
Dr. Tanvi Sachar
Monday Certified Partner, Tuesday Wizard
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
