(In reply to mbagnara from comment #0) > ... Thank you for filing this bug report. I'd like to ask for some more information to help us narrow down the source of this bug: 1. Do you experience this bug with only one calendar or more than one? 2. Is this problem consistent? Can you reproduce easily or does it seem to be arbitrary. 3. How many Google calendars do you have on your profile already? Are they in use with a lot of events? 4. Is it limited to Google CalDav calendars? Have you experienced this with other providers? Are you able to try? 5. Are there any repeating events on the offending calendar(s)? 6. Did the 403 error have any response body? What did it say? I'm trying to determine if this is strictly an authentication issue or perhaps a rate limit problem. If it turns out to be the latter, re-authenticating probably won't resolve the issue. If you feel comfortable getting more technical with Thunderbird, you can enable the `calendar.debug.log` pref that would provide you with a little more information useful in further determining want went wrong.
Bug 1789424 Comment 1 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 mbagnara from comment #0) > ... Thank you for filing this bug report. I'd like to ask for some more information to help us narrow down the source of this bug: 1. Do you experience this bug with only one calendar or more than one? 2. Is this problem consistent? Can you reproduce easily or does it seem to be arbitrary. 3. How many Google calendars do you have on your profile already? Are they in use with a lot of events? 4. Is it limited to Google CalDav calendars? Have you experienced this with other providers? Are you able to try? 5. Are there any repeating events on the offending calendar(s)? 6. Did the 403 error have any response body? What did it say? 7. (Edit) Additionally, does your subscription to Google services fall into one of these categories? a. Paid subscriptions up to 60 days after meeting the payment threshold b. Trial accounts c. Users of the legacy free edition of G Suite d. Customers of Google for Nonprofits I'm trying to determine if this is strictly an authentication issue or perhaps a rate limit problem. If it turns out to be the latter, re-authenticating probably won't resolve the issue. If you feel comfortable getting more technical with Thunderbird, you can enable the `calendar.debug.log` pref that would provide you with a little more information useful in further determining want went wrong.