Google Calendar Has A Quota?
Oh, boy, ladies and gents, this one is a doozy. Michel can’t get into his Google Calender, apparently because he is over his Calendar’s quota. Google Calendar has a what?
His blog post, translated from Dutch by a buddy:
Google Quota?
Hmm, what have we here? Did Google Calendar start up a quota system or something alike?
Before - until yesterday - I could check periodically whether my calendar changed or not, and by means of API i could insert or remove things. Not any more, so it seems. I can do it for a while, but then at a certain time it says:
Google autoSync failed
Sync with Google failed:calUserID:8768 sync() error. Google ServiceException:com.google.gdata.util.ServiceForbiddenException
message:calUserID:8768 You have hit Google’s quota limit.Hm. Apperently the time of “everything’s possible” is clearly over.
Very interesting. Does Google have some sort of quota for Calendar? Is the quota related to Gdata API requests? The first commenter says, “I have those errors already for a while”. The fourth commenter adds, ” I can’t get it synced anymore… used to work with outlook 2003, the 2007 outlook doesn’t do it anymore: doesn’t seem to cooperate with the funambol plugin”.
You know, Outlook doesn’t have a quota. That’s all I’m going to say.
UPDATE: Lane LiaBraaten from the Google Calendar team showed up in the comments to explain what’s going on. Basically, some applications using the API delete and recreate the entire Calendar, every time they sync with it, rebuilding the whole freakin’ thing for some reason. Crazy! So, those applications wind up creating tons of cancelled events in the Calendar every time they sync, flooding it with thousands of cancelled events, so yeah, Google shuts them down. What do you expect? It’s practically an attack on the system!
Thanks for clearing that up, Lane!
That’s weird. I’ll ask someone about it.
Comment by Matt Cutts | April 25, 2007
Just one thing: I do still have access to my calendar via the web interface. It’s my automagical Outlook/Google Calendar syncronisation via Funambol that doesn’t seem to be working anymore.
Comment by Michel Vuijlsteke | April 26, 2007
Google Calendar Has A Quota? » InsideGoogle
有用戶使用Google Calendar出現爆Quota問題
Trackback by pligg.com | April 26, 2007
SearchCap: The Day In Search, April 26, 2007
Below is what happened in search today, as reported on Search Engine Land and from other places across the web:…
Trackback by Search Engine Land: News About Search Engines & Search Marketing | April 26, 2007
Hi,
A number of people have raised this issue in the Calendar data API group. The error usually occurs when developers implement syncing applications that delete and then recreate all of your calendar events at once. When an event is deleted using the Calendar data API, it is marked as canceled and remains in the system, which is likely what’s triggering this quota error. Once a week, a reaper comes through and clears the canceled events out for good, which puts your calendar back in good shape. For more information on this or if you have additional comments or questions, please visit the Calendar data API group.
Hope that clears things up,
Lane LiaBraaten
Google Calendar Team
Comment by Lane LiaBraaten | April 26, 2007
To Lane:
Is there a list of what applications that had the behavour you mentioned? I am all for using applications to handle GCal within reasonable limits, but if some apps are causing problems like this, I would like to avoid them in the first place.
Felix
Comment by Felix | April 26, 2007
Sorry, I don’t have a list of what syncing stategies different applications are using. You can probably find out more information if you look at the documentation or support community of any sync application you’re planning on using.
Cheers,
Lane
Comment by Lane LiaBraaten | April 30, 2007
FYI ScheduleWorld does not do this.
ScheduleWorld very carefully only transmits changes to Google, and only requests changes from Google.
Note: You can configure ScheduleWorld to do a one-time full (slow) sync but ScheduleWorld will only perform this operation once and then revert to the “changes only” two-way sync.
Cheers.
Comment by Mark Swanson | July 11, 2007
One more thing. The Funambol Outlook plug-in can be configured to do a one-way sync through ScheduleWorld to Google - and it can be scheduled to automatically do this every x minutes.
A one-way (replace server data) sync works like this:
1. delete all events on the server
2. send all events to the server.
So some folks might be creating a lot of deleted entries on Google without even realizing it. This is one reason why you shouldn’t schedule one-way syncs and you should use normal two-way syncs instead.
Cheers.
Comment by Mark Swanson | July 11, 2007
Not really correct.
A one-way (client to server) sync works like this:
- send new/modified/deleted items only from client to server. With Outlook Plug-in you can schedule two-way or one-way sync.
What you are talking about is a refresh-from-client sync, that can be started from plugin menu “tools > recover”. These kind of sync CANNOT be scheduled (they’re used to recover data).
Cheers,
Andrea
Comment by Andrea Tocclaini | July 12, 2007