Before posting, and to avoid disappointment, please read the following:
This forum is not for 2BrightSparks to provide technical support. It's primarily for users to help other users. Do not expect 2BrightSparks to answer any question posted to this forum.
If you find a bug in any of our software, please submit a support ticket. It does not matter if you are using our freeware, a beta version or you haven't yet purchased the software. We want to know about any and all bugs so we can fix them as soon as possible. We usually need more information and details from you to reproduce bugs and that is better done via a support ticket and not this forum.
If you are entitled to technical support then please submit a support ticket. Please do not post the same question to the forum and also via a support ticket. Once again, 2BrightSparks does not provide technical support via this forum.
I've just started to receive failed Cloud backup jobs with an error of:
rateLimitExceeded: Quota exceeded for quota metric 'Queries' and limit 'Queries per minute' of service 'drive.googleapis.com' for consumer 'project_number:PROJECT_NUMBER_HERE'.
I've noted the 'queries per minute' part of the message. Is there a way to rate limit the querying from within Syncback? I can see there's a bandwidth limiting option, but not query limits.
Running on Windows 10, with SyncbackPro v8.9.15.0 64-bit.
Meaning, are you saying that you've had two in a row that were successful? Because I'm still seeing the alternating pass/fail pattern when conducted every 24 hours, the very same pattern that you first pointed out. It's happened enough now that it's not happenstance, and Google reverting whatever they did a few days ago (see tweet above) has had no effect.
If only there were someone besides us who uses the product.
Just to break into this extremely busy thread with an update, the error cadence is more every than every other day now, but it may not matter, since I noticed that it seems that everything that is meant to happen in terms of uploads etc do seem to happen. In other words, it may be more of a cosmetic error, or perhaps an early warning before it truly goes south.
Yes, that is is interesting, so it was due to the changes Google made after all, changes that they seemed to publicly backtrack on weeks ago but maybe didn't fully? It always did seem to be too much of a coincidence that this started happening at just about the same time as that.
Is it a daily quota?
Also as mused about above, what is the reason that everything does seem to be synced despite the warning/error?
I followed the steps in the blog post and got a secret key, but stuck on UNAUTHORIZED_CLIENT.
Google Cloud forces me to input a domain, and since I don't own 2brightsparks domain either, I can't pick this one, this will never pass Google's verification...
What should I do?
Attachments
Screenshot_20230619-074003_Opera.jpg (477.95 KiB) Viewed 6015 times