Changes to a repeating event now reach your other calendars

· v2.13.5

Repeating events are the ones a calendar gets wrong quietly. The original series copies across correctly, and then someone changes it — the weekly call moves an hour later, a date gets skipped, the whole thing shifts when the organiser changes timezone — and the copies carry on describing the old arrangement. Nothing errors, so nothing tells you the two calendars stopped agreeing.

Changes to a series now reach the copies. Editing the repeat rule updates them, skipping a single date removes that occurrence rather than leaving it stranded, and moving the series to another timezone moves every occurrence with it rather than shifting the first and leaving the rest behind.

Single occurrences are handled as their own thing. Moving next Tuesday's instance of a weekly meeting changes next Tuesday, and the rest of the series stays where it is — which is what the original calendar does, and therefore what the copy should do.

Read more about everything Keeper.sh does.

Improved

  • Each calendar you sync into runs on its own, so a slow one no longer holds up the rest.

Fixed

  • Events you marked as free show as free in the feed you share.

  • The home page no longer sits on Syncing long after a sync has finished.

  • A deleted event is no longer left behind when the lookup that finds it fails.

  • Replying to one occurrence of a repeating invitation no longer changes the rest.

  • mailbox.org calendars connect on the first try.

  • An event with no series identifier no longer stops a sync.

  • A request that stops responding is given up on after 30 seconds, so the sync finishes.

  • A rescheduled event no longer leaves the old copy behind on your other calendars.

  • A sync running over two minutes keeps its claim on the calendar it is writing to.

Can Keeper.sh use cookies for analytics?