(In reply to Richard Leger from comment #25) > Wouldn't such situation happen again in the future? We'll keep an eye on it. The limit has been raised to 50x its prior amount though, so we should be good for some time. > Wouldn't the 403 error code received from Google be accompanied by a message like "User Rate Limit Exceeded"? Well, part of the confusion here is that Google is misusing errors. 403 has a distinct meaning, it means you are unauthorized to access the resource at the URL. The correct error code for rate limiting is 429. And in addition, they weren't including any additional information in the body of the response, it was just blank. So no, the answer is Google's error messages for CalDav are terrible and you can't expect them to make any sense. > Shouldn't that allow TB to identify the issue during the sync[...]? Improvements to the way Calendar handles sync errors were made in Bug 1792923 as a result of this bug.
Bug 1789424 Comment 26 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Richard Leger from comment #25) > Wouldn't such situation happen again in the future? We'll keep an eye on it. The limit has been raised to 50x its prior amount though, so we should be good for some time. > Wouldn't the 403 error code received from Google be accompanied by a message like "User Rate Limit Exceeded"? Well, part of the confusion here is that Google is misusing errors. 403 has a distinct meaning, it means you are unauthorized to access the resource at the URL. The correct error code for rate limiting is 429. And in addition, they weren't including any additional information in the body of the response, it was just blank. So no, the answer is Google's error messages for CalDav are terrible and you can't expect them to make any sense. > Shouldn't that allow TB to identify the issue during the sync[...]? Improvements to the way Calendar handles sync errors were made in Bug 1792923 as a result of this bug.