Closed Bug 1791517 Opened 3 years ago Closed 3 years ago

Calendars lose synchronization and get disabled

Categories

(Calendar :: Provider: CalDAV, defect)

Thunderbird 102
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1789424

People

(Reporter: pufiad, Unassigned)

Details

Steps to reproduce:

Thunderbird 102.2.2 (64-bit)
Mozilla Thunderbird for Arch Linux archlinux - 1.0

  1. Add some Gmail calendars with Caldav, using links that start with https://apidata.googleusercontent.com/caldav/v2/

  2. Set them to:

  • refresh every 15 or 30 minutes;
  • NOT read only; show reminders;
  • offline support enabled;
  • prefer client-side email scheduling

Actual results:

Before version 102 the calendars showed always fine all events.

Since version 102 the Gmail calendars often (a few times per day) lose synchronization, the calendars are disabled and all events disappear.

Enabling the calendars and synchronizing them does not always bring the calendars back.

Expected results:

  1. Synchronization should not be lost.

  2. If synchronization is lost, the calendar should not be disabled.

  3. Since offline support is enabled, if synchronization is lost, the events should not disappear (should not be hidden).

Component: Untriaged → Provider: CalDAV
Keywords: dupeme
Product: Thunderbird → Calendar

It's not because of 102, it's because we keep hitting Google API rate limits. We're working on a solution to this and the disappearing events.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE

Thank you, Geoff. Do you know what the rate limits are? Are they per IP address?

It's for all Thunderbird users, not per-IP. We're hitting the limits when the highest numbers of users are online, about 0800-1000 UTC. We've asked Google to lift our limit.

Who would have thought that! What technical reason can there be for such a limit?

What does Google check? The user agent string?

They check how many requests there are to the API. I guess so they can ensure scaling etc.

You need to log in before you can comment on or make changes to this bug.