When a calendar stops syncing, the cause is almost always one of five things: the account connection has expired, the wrong calendar is selected, the permission is read-only, the timezone is off, or the change simply hasn’t arrived yet. Check them in that order and you will fix most problems in minutes. For an escape room, a sync fault is more than an annoyance, because a stale calendar is how a double booking happens. This guide covers the checks that work on any device, then the extra steps for venues that connect a booking system to Google, Outlook or Apple calendars.
TL;DR
- Start with the basics: internet connection, app updates, the correct account, and whether the calendar is switched on and visible.
- Work out where the break is. Check the calendar in a web browser to see whether the fault sits between the booking system and the calendar, or between the calendar and your phone.
- A constant offset of a set number of hours, or exactly one hour after daylight saving changes, points to a timezone mismatch, not a failed sync.
- Expired or revoked authorisation is the most common reason a connection quietly stops. Reconnect the account rather than deleting and rebuilding everything.
- For booking calendars, prefer one-way sync so your booking platform stays the single source of truth for availability.
Table of Contents
- Check the basics first
- Find out where the sync is breaking
- The five causes that explain most failures
- Platform-specific fixes
- Missing events, duplicates and odd behaviour
- Why one-way sync suits escape rooms
- A weekly routine that catches problems early
- Quick diagnosis table
- Our perspective
- Keep availability accurate with Riddlio
- FAQ
- Sources
Check the basics first
Most sync complaints are solved before any advanced step. Google’s own guidance for the Android app is a short list: confirm your internet connection, update the Calendar app and check that the calendar is visible. It also tells you to make sure new events are being added to the calendar you expect, that Calendar sync is turned on in your device settings, and to refresh manually from the menu.
Work through this checklist in order:
- Connection. Switch between Wi-Fi and mobile data. Airplane mode, a weak signal or a captive Wi-Fi login page will all stop a sync without any error message.
- App and system updates. An outdated calendar app or operating system can fail to talk to a calendar server that has changed.
- Right account. Many people have two or three accounts on one phone. Confirm the account you are looking at is the one that holds the events.
- Visibility. A calendar that is unticked in the app’s list is hidden, not broken. Tick it and look again.
- Sync switch. Check that calendar sync is enabled for that account in the device’s account settings.
- Storage. A phone that is completely full may stop syncing calendar data, so clear some space if the device is nearly out of room.
- Manual refresh. Use the refresh option in the app, or close and reopen it.
If you do this and a single new event is the only thing missing, wait a little. Sync is not instant, and a booking made seconds ago can take time to show up elsewhere. Treat a delay as a real fault only when it persists well beyond a normal wait, or when everything is affected rather than just the newest item.
Find out where the sync is breaking
Before you change settings, find the broken link in the chain. A typical venue has three links: the booking system, the calendar service (Google, Outlook or iCloud), and the device where staff read the calendar.
The quickest test is to open the calendar in a web browser on a computer:
- Event is in the browser but not on the phone. The booking system is fine. The fault is between the calendar service and the device. Work through the device checks above.
- Event is missing in the browser too. The fault is between the booking system and the calendar service. Look at the connection, the selected calendar and the permissions.
- Event appears in the browser under another calendar. The wrong target calendar is selected in the connection settings.
One rule saves a lot of pain: don’t delete and recreate the connection repeatedly, and don’t copy events into the destination by hand. Both create duplicates and make it harder to see what actually went wrong. Change one thing, wait, and check again.
The five causes that explain most failures
1. Expired or revoked authorisation
When you connect a calendar, you grant the booking system permission to read or write on your behalf. That permission can lapse. A password change, a security prompt, an admin policy or a staff member removing app access will break it. Events then stop moving in either direction, often with no warning.
The fix is to disconnect and reconnect that single account from the booking system’s integration settings, signing in with the account that owns the calendar and accepting every permission requested. Choose “allow” for the ability to edit, not just view.
2. The wrong calendar is selected
Google and Outlook accounts often hold several calendars: a personal one, a shared team calendar, a holiday calendar. If your integration writes to the personal one, staff looking at the team calendar will see nothing. Open the integration settings and confirm which calendar receives bookings. Then confirm that same calendar is ticked on the device.
3. Permission allows viewing but not editing
Shared calendars are a classic trap. If a calendar was shared with you as “see all event details”, a booking system cannot add events to it, and events shared from another calendar without read and write access may not sync back either. Ask the calendar owner to change your access level to one that can make changes, or connect an account that owns the calendar.
4. Timezone mismatch
If events appear but at the wrong time, don’t treat it as a sync failure. A consistent offset, such as a fixed number of hours off for every event, or exactly one hour off after a daylight saving change, is the signature of a timezone setting that disagrees somewhere in the chain. Check three places: the venue timezone in your booking system, the timezone of the connected calendar, and the timezone on the device. They must all describe the same location. This matters for venues with several sites in different US timezones, where each location needs its own correct setting.
5. Normal propagation delay
Some services push changes to each other immediately. Others check for changes at intervals. An event booked a minute ago may not show on a phone that is polling every so often. A stale view also cannot prove that a slot is free. That is why the booking system, not a calendar subscription, should confirm whether a time is available.
Platform-specific fixes
Google Calendar
After the basic checks, open Google Calendar in a browser and verify the event exists there. On Android, confirm sync is enabled for the account in the device’s account settings. Remove and re-add the account only as a last step. For escape room specifics, see our practical Google Calendar sync guide.
Outlook and Microsoft 365
Microsoft notes that POP and IMAP accounts do not support calendar sync. If your email is set up that way, you will never see calendar events move between devices, however many times you refresh. Microsoft’s guidance is to check that Calendar is enabled for the account in the Outlook app, reset the account if it isn’t syncing, or delete and re-add the email account. Our walkthrough of Outlook calendar sync for escape room operators covers the venue side.
Apple Calendar and iCloud
Check that every device is signed in to the same Apple Account with Calendars switched on, that each device is up to date, and that the date and time settings are correct. Apple also publishes a system status page, so confirm iCloud Calendar isn’t having an outage before you change anything. Subscribed calendars on Apple devices can refresh slowly, which is why we wrote about how to stop long sync delays in Apple Calendar.
Missing events, duplicates and odd behaviour
Some gaps are by design, so check the rules before you assume a bug. Many booking tools that sync with Google ignore all-day events, events spanning several days, events far in the past, and events further ahead than a set window. If you block a whole day for maintenance using an all-day event, the booking system may not treat it as busy. Create a timed block covering your opening hours instead, or block the day inside the booking system itself.
Missing events. Check the filters first: is the calendar visible, is the date range sensible, and is the event in a calendar you haven’t connected? Then check whether the event type is one that doesn’t sync.
Duplicates. Duplicates usually appear when an event is created in one system, copied to another, and then copied back as if it were new. Two-way sync with several tools editing the same entries makes this worse. The cure is a stable booking ID that never changes, even when the time or customer details do, and a setup where only one system owns each booking. AppMaster’s guide to syncing booking apps explains this clearly.
Wrong details. If a title or customer name is missing, check whether the connection is set to share only busy or free status. That setting removes details on purpose.
Edits that don’t come back. In many setups, moving an event in the calendar doesn’t update the booking. That is normal for one-way sync, and the safe choice for a business whose bookings carry payments, waivers and group sizes.
Why one-way sync suits escape rooms
Two-way sync sounds convenient, but it creates the most puzzling failures, because different tools interpret edits differently and conflicts multiply when several people change the same entry. One-way sync is the safest setup when you want clear control: staff see their day in their own calendar, while bookings, reminders and availability remain owned by the booking app.
For a venue, that translates into simple house rules:
- Bookings are created, moved and cancelled in the booking system only.
- Staff calendars are read-only views of the schedule.
- Personal commitments that block a game master are entered as timed blocks in the booking system or on a dedicated calendar that is connected for availability.
- Nobody drags booking events around in a phone calendar.
These rules remove the largest source of drift between systems. For a wider fix on double bookings, read our guide to preventing double bookings at activity venues.
A weekly routine that catches problems early
Sync faults hurt most when nobody notices them for days. A five-minute routine helps:
- Create a test booking on a quiet slot and confirm it appears in the staff calendar and the right room.
- Cancel it and confirm it disappears.
- Compare tomorrow’s schedule in the booking system with the staff calendar.
- Check that the connected account’s authorisation is still active in your integration settings.
- After any daylight saving change, check one event’s time end to end.
If you change your email password, move staff to a new account or alter admin policies, run the same test straight away.
Quick diagnosis table
| What you see | Most likely cause | First fix |
|---|---|---|
| Nothing syncs at all | Expired or revoked authorisation | Reconnect the account and accept all permissions |
| New events missing, old ones fine | Delay or wrong calendar | Wait, then confirm the target calendar |
| Events show at the wrong hour | Timezone mismatch | Align venue, calendar and device timezones |
| Events can’t be added to a shared calendar | Read-only permission | Ask for edit access or use the owner’s account |
| Event shows on web, not on phone | Device sync problem | Update app, check sync switch, refresh |
| Events appear twice | Two systems writing to each other | Switch to one-way sync, keep stable IDs |
| Titles and details are blank | Busy-only sharing mode | Change the sharing level in the connection |
| Block-out days ignored | All-day events not imported | Use timed blocks instead |
Our perspective
Most calendar sync trouble we see comes from asking a calendar to do a booking system’s job. A calendar shows time. It doesn’t know a room’s player limits, a group’s deposit, or whether a waiver is signed.
That is why we built Riddlio around the booking system as the source of truth. Availability, room capacity, payments and customer messages live in one place, and calendars are a convenient window onto that schedule. We recommend one-way sync for staff calendars, so a swipe on a phone can’t create a clash that a customer then books into.
When something does look wrong, the habit that serves venues best is to check the booking system first. If a slot is open there, it is open. Everything else is a view that may be catching up.
Iosif Beraru
Keep availability accurate with Riddlio
If you troubleshoot sync every week, the setup is working against you. Riddlio is a booking and management platform built for escape room venues, bringing bookings, availability, payments, customer communications and reporting together, with calendar sync to keep your team’s schedule visible. Our online booking calendar for escape rooms is where availability is managed, so a delayed calendar never decides what customers can book.
Plans are published on our pricing page: Starter is $29 per month, Pro is $79 per month and Unlimited is $199 per month, with Enterprise available on request. You can also reduce no-shows with automated SMS reminders so the schedule you protect is the schedule that turns up.
FAQ
Why is my calendar not syncing between devices?
The usual causes are a connection problem, a different account on one device, a calendar that is hidden, or sync switched off in the account settings. Check those first. If the event shows in a web browser but not on the device, the fault is on the device side.
How do I force a calendar to resync?
Use the refresh option in the calendar app, close and reopen it, or turn the account’s calendar sync off and on again. Google’s guidance includes a manual refresh from the app menu. Avoid deleting and rebuilding the connection repeatedly, since that can create duplicate events.
Why are some events not syncing while others do?
Check the event type and the calendar. All-day events, multi-day events and events well outside the sync window often don’t import into booking tools. Events on a shared calendar with view-only access won’t write back either.
Why do my synced events show at the wrong time?
A fixed offset is nearly always a timezone setting, not a sync failure. Compare the timezone in your booking system, the connected calendar and the device. After a daylight saving change, a one-hour shift points to the same cause.
How do I stop double bookings caused by sync problems?
Make your booking system the only place where bookings are created and changed, use one-way sync to staff calendars, and give each booking a stable ID. Confirm availability from the booking system itself, never from a calendar view that may be out of date.
Sources
- Fix sync problems with the Google Calendar app (Google Calendar Help)
- Can’t sync calendar and contacts with my phone or tablet (Microsoft Support)
- Calendar syncing for booking apps: avoid double entries (AppMaster)