Skip to main content
Best answer

Zap running twice within seconds


We have a zap that runs when a record is updated, if a particular field is set to yes then it copies a document to another table.  This was working fine until a few months ago and now it runs twice every time and copies the file twice, I see in the log file that it ran twice within a matter of seconds.

Has anyone else experienced this issue?

Best answer by SamB

Just to follow up on this one, it looks as though our Support team were able to identify the cause of the issue. It was related to an existing bug with the Caspio Cloud Database integration where updated records are triggering twice. @ELN24 was added to the bug report for this issue.

For anyone who may also be running into the same issue, please contact our Support team. They’ll be able to dig into the logs for your Zap to confirm whether you’re being affected by the same issue and add you to the bug report as necessary.

In the meantime, there’s an article in Community for a workaround to help with duplicate triggers that may be worth trying while the bug is still active:

 

View original
Did this topic help you find an answer to your question?
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

Troy Tessalone
Forum|alt.badge.img+14

Hi @ELN24 

What is the Zap trigger app?

 

Might be best to open a ticket with Zapier Support for them to troubleshoot further: https://zapier.com/app/get-help


AndrewJDavison_Luhhu
Forum|alt.badge.img+10

@ELN24 
Just checking in to see if you still need help with this? 


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • 7442 replies
  • Answer
  • September 9, 2021

Just to follow up on this one, it looks as though our Support team were able to identify the cause of the issue. It was related to an existing bug with the Caspio Cloud Database integration where updated records are triggering twice. @ELN24 was added to the bug report for this issue.

For anyone who may also be running into the same issue, please contact our Support team. They’ll be able to dig into the logs for your Zap to confirm whether you’re being affected by the same issue and add you to the bug report as necessary.

In the meantime, there’s an article in Community for a workaround to help with duplicate triggers that may be worth trying while the bug is still active: