About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

Why is this Google Calendar Zap using so many tasks?

  • 29 August 2021
  • 1 reply
  • 47 views
A

I created this Zap to be triggered when there are New or Updated events in my Google Calendar. The intended goal of the Zap is to add a specific invitee to every event (the invitee is hard-coded, i.e., it’s always the same one). Unfortunately, there’s something wrong the Zap because it has used more than 1,000 tasks in less than 24 hours. I have certainly not created or updated 1,000 events. The part that I’m least sure about is the action set up. I’m pasting a screenshot below:

I should mention that the Zap seemed to be doing what I wanted it to do. However, it stoped now because I ran out tasks.

icon

Best answer by SamB 19 November 2021, 12:18

View original
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

1 reply

SamB
Rank
Userlevel 7
Badge +11

Just wanted to follow up here as spotted that @andresmh also reached out to Support about this and it appears to have been related to a Zap loop that caused the accidental Task usage. The Zap was using the Event Updated trigger and adding attendees to the event. This then caused the Zap to trigger for the same event again as the new attendee was seen as a being a new update to the event. 

The Zap loop has since been fixed but for anyone experiencing similar issues I’d recommend checking out our Zap is stuck in a loop guide to find out more about Zap loops and how to prevent them.

And if you’re still having issues after following the steps in that guide, please do reach out to our Support Team via the Get Help form and they’ll be happy to assist further! :)

Terms & Conditions