Sudden flurry of zaps - and I can't see that we caused it
Yesterday there was a sudden flurry of executions in one of my zaps. None of these were intentional as far as I can see, and I’m well aware that they can run unintentionally if sheet (Google sheet) is re-ordered or rows deleted, none of which I did. What can have gone wrong here?
We normally have low transaction volumes and are therefore running the 100 runs per month plan, which no longer provides support from Zapier, som I’m posting the question here in the hope that someone can help me out.
Ideally, since this flurry wasnt due to anything at our end as far as I can see, I’d hope to see Zapier restore the number of available zaps.
Thanks,
Lars.
Page 1 / 1
Hi @Hornborg
For us to have full context, we would need to see screenshots with how your Zap trigger step is configured.
Check your Zap Runs timestamps for clues as to when the change may have happened.
This post has been edited by a moderator to remove personal information. Please remember that this is a public forum and to remove any sensitive information prior to posting.
Here’s the trigger step (first image) and the run log (second image)
Yes, I’m aware of that, and these workflows have been running un-edited for three years with no problem. Now, today, this happened again. As you can see in the screenshots I supplied, I’m using the New or updated row trigger, and monitoring the column “Medlems-kod”. Again, this has worked flawlessly for ages, and now - today - my full montly quota is exhausted.
So since I haven’t changed anything at all in the sheet setup, nor in the zap, what is going wrong here. I’d really hope to see Zapier restore my quot because right now the system it’s serving is crippled.
I’m so sorry to hear of the troubles here. I just wanted to clarify that it’s possible to reach out to the Support team regarding any account/billing related issues while on a Free plan. If you go to the Contact page here and scroll to the bottom you should see a What would you like more help with? section:
From there you can select the Accounts, pricing and billing option to have your request routed through to the Billing and Accounts team who can assist with those sorts of issues.
Regarding the Zap triggering unexpectedly let’s see if we can narrow down what might have caused that.
Hmm, as the times of each run appear to be identical I’m wondering if a new row was inserted somewhere above the bottom row causing the rows below it to change their row number/ID and be “seen” by the Zap as a new row that it needed to trigger on. I know you mentioned that the set up hadn’t been changed but do you think someone who has access to the spreadsheet may have added a new row in like that?
