Hello, we just started getting the following error for all our users.
Could you please explain what is going on? We're still using v2 api.
google.gdata.util.ServiceException: Service Unavailable
Temporary problem - please try again later. The user is over quota.
Thank you for contacting Fieldston Software product support.
Your request will be reviewed as soon as possible.
While we do our best to respond to requests as soon as they arrive some requests may take 24 - 48 to receive a response.
If this is a "User Reported Error" issued from within our application please note that these reports are managed in a different support queue and you may not receive a response. It is best to email support directly and reference that you've also reported the error to us.
Thank You.
Support @ Fieldston Software
____________________________________________________________
John
> --
> You received this message because you are subscribed to the Google
> Groups "Google Contacts, Shared Contacts and User Profiles APIs" group.
> To post to this group, send email to
> google-co...@googlegroups.com
> To unsubscribe from this group, send email to
> google-contacts...@googlegroups.com
> For more options, visit this group at
> http://code.google.com/apis/contacts/community/forum.html
Seems to be working well now. This just is not well documented for the
contacts API, I found references to this somewhere else.
Cheers
On 4/16/12 10:55 PM, "Donald" <donald...@gmail.com> wrote:
> 48+ hours later, the GData Contacts API continues to be problematic.
> While I've been able to get around some of the problems by rewriting
> my code to batch 100 contact operations into each ticket, my requests
> to download and upload photos continue to fail for the most part, and
> I don't think there is a way to batch photo uploads and downloads. Is
> Google imposing a rate limit on how many photos we can request per
> second? Would Google consider lifting this rate limit or at the very
> least making the rate limit per hour instead of second? Having a limit
> of perhaps 5000 photo downloads/uploads per hour seems like a better
> approach than setting a limit of perhaps 2 contacts per second which
> seems to be the current behavior.
>
> In addition to the problem with photos, requests to create multiple
> contact groups with a batch operation often come back with only some
> of the groups having been created, so my app has to detect that case
> and then submit another batch operation (up to 5 times in my
> experience) to get all of the contact groups created.
>
> Google, if you could get to the bottom of these issues, I would really
> appreciate it!
>
> On Apr 16, 9:35 am, Donald <donald.law...@gmail.com> wrote:
>> Google, is there any information you can give us about these mysterious
>> errors that just started occurring? It has created a big problem for us.
>>
>>
>>
>>
>>
>>
>>
>> On Sunday, April 15, 2012 12:54:41 AM UTC-7, Donald wrote:
>>
>>> I'm getting similar errors for my contacts sync app for the iPhone. Is
>>> there a quota on contacts now?
>>
>>> On Saturday, April 14, 2012 11:14:09 PM UTC-7, Alexey Panteleev wrote:
>>
>>>> Ok, going to put rate limiting handling in place ...
>>
1. Photo requests failing. As Donald reported, the limit seems to be
roughly two requests per second. When I throttle back my photo
requests to two requests per second, I no longer see photo requests
failing.
2. I am getting 503 responses to login requests via ClientLogin where
I have issued a large number of requests for either the contact list
or contact photos. In one case, the issue is a test account with a
large number of contacts. I have been exercising the Contacts API on
this test account extensively in an effort to deal with this problem.
However, in another case one of my customers is encountering this with
my software.
I am eager to work within Google's guidelines, but am frustrated to
not know what they are. Are we limited by number of requests per
second, minute, hour, or day? Or by bytes served per second, minute,
hour, or day? Since Google is not publishing this information, the
only way to determine this is by experimenting. Experimenting only
means throwing excessive requests to the Contacts API to see where the
API stops serving us.
John