Question

Single-step zap ran 3 times for one action - not sure why

  • 29 September 2023
  • 5 replies
  • 28 views

Hello,
We have a single-step zap set up so that when we update a client profile in one database, it updates that client profile in a second database.  
We noticed that for a couple of client profiles, one update created 3 different zap runs (and was also counted as 3 separate tasks as a result).  
We can’t figure out why this zap ran 3 times for a single update, and also how to stop this from happening.  We have exceeded our usage for this month because of all these extra zaps and don’t want this to happen again.  

Please help!  

Here is a screenshot of the zap configuration:
 

 

 

 


5 replies

Userlevel 7
Badge +14

Hi @Client Care 

Good question.

We would need to see detailed screenshots of these:

  • Zap Steps configuration
  • Zap Runs DATA IN/OUT

Hi @Client Care 

Good question.

We would need to see detailed screenshots of these:

  • Zap Steps configuration
  • Zap Runs DATA IN/OUT

Thanks, Troy--i have added a screenshot for the zap configuration, is this what you need?
And can you tell me how to find the data in/out information?  

Userlevel 7
Badge +14

@Client Care 

Check your Zap Runs: https://zapier.com/app/history/

There you will be able to see the DATA IN/OUT for each Zap step.

Userlevel 7
Badge +14

@Client Care 

Looks like you are using an outdated version of the Chime Zap app.

 

Make sure to connect and update the Zap step to use the version without the version #. (1.0.6)

 

Userlevel 7
Badge +14

@Client Care 

Mojo may sent an update for each unique field updated. (TBD)

 

Reply