Sync starts the moment you connect a calendar

· v2.9.34

Connecting a calendar used to end in a wait. The account was linked, the calendars were listed, and then nothing visibly happened until the next scheduled run came around — which on the free plan could be half an hour of staring at an empty destination wondering whether the setup had worked.

Connecting now triggers a sync straight away. Events start arriving while you are still on the page, which turns the first minute after setup from a question into a confirmation, and means a mistake in your mapping shows up immediately rather than after the delay.

The same applies when you change something that affects what gets copied. Adjusting which calendars feed a destination asks for a sync rather than waiting for the schedule to notice, so the thing you just changed is the thing you can go and check.

Read more about everything Keeper.sh does.

Improved

  • Access for each account is renewed one request at a time, so accounts stay signed in.

  • Google's working from home entries are always left out, and the option to include them is gone.

  • Large Google and Outlook calendars are fetched in smaller pages, so they stall less often.

  • The check your email screen reminds you to look in spam or junk.

  • A calendar link that comes back unchanged is no longer rebuilt from scratch.

  • Keeper.sh runs many more syncs at once, and a repeat sync replaces the one already waiting.

Fixed

  • You can delete your account when you signed in with Google or Microsoft.

  • A request for events between two times returns exactly that window.

  • Times read correctly in zones with a single-digit offset, such as Montevideo.

  • Repeating events show every occurrence in your Keeper.sh feed, not just the first.

  • All-day events read as all-day in the feed Keeper.sh publishes.

  • Calendar and feed settings save the value you typed.

  • Sync progress only moves forward, and reaches the end when the sync is done.

  • An event already sitting in the calendar you sync into is replaced with the current version.

  • Keeper.sh waits and retries the way Google asks when it is being rate limited.

  • Ordinary hiccups from a CalDAV server no longer ask you to reconnect.

  • Events land in the calendar you chose, not the default one, and stop repeating.

  • An account that returns no email address now connects.

  • Events no longer fail when Microsoft returns no identifier for them.

  • Calendar links hosted by Google load again.

  • A calendar you turned off is no longer synced on every scheduled run.

Can Keeper.sh use cookies for analytics?