Calendar not syncing? Troubleshooting

If a block isn’t appearing in Rezi, it’s almost always one of a few things. Work through these in order.

Some orientation before you start: calendar problems are nearly always feed problems, either Rezi can’t read the feed (bad or private URL), the feed doesn’t contain what you expect (platform hasn’t republished, or the block lives on a different listing), or the feed was never connected where you think it was. The checks below are ordered from most to least common, and the whole sequence takes about five minutes.

1. 1

   Confirm the URL is public

   The iCal link must be accessible without a login. Paste it into a private browser window, if it downloads an .ics file, it’s public.

2. 2

   Give it 15 minutes

   If you just connected or just booked, wait one sync cycle. The platform also needs time to refresh its own export.

3. 3

   Trigger a manual sync

   Use the manual sync button on the Calendars tab to force an immediate refresh.

4. 4

   Re-copy the link

   Platforms occasionally rotate export URLs. If it still fails, re-copy the link from the source and paste it again.

Why each check matters

The private-window test catches the single most common mistake: copying the calendar page’s address from your browser bar (which needs your login) instead of the export link the platform generates. Rezi fetches feeds without credentials, so a login-walled URL yields nothing. If your private window shows a login page instead of downloading a file, you’ve found the problem, go back to the platform’s “export calendar” flow and copy the actual .ics link.

The waiting step exists because of the two-clock latency: the platform republishes its file on its own schedule, then Rezi re-reads it within 15 minutes. A booking made two minutes ago genuinely isn’t in anyone’s feed yet. Manual sync removes Rezi’s half of the wait, useful for testing, but it can’t make the platform publish faster. Re-copying the link fixes silent URL rotation, which platforms do after certain listing edits; the old URL often keeps returning stale data rather than failing loudly, which is why this one is sneaky.

Less common culprits

If the basics check out, widen the search. Confirm the feed is attached to the right property, a feed pasted onto the wrong property produces blocks that exist but in the wrong place. Confirm the block lives on the listing whose feed you connected, a date blocked on your VRBO listing will never appear via your Airbnb feed; each platform needs its own feed. And if dates are wrongly *blocked* rather than wrongly free, check for a forgotten manual block or a canceled reservation the platform hasn’t republished yet.

Preventing the next incident

Three habits make calendar issues rare. After any significant listing edit on a platform, glance at the feed’s last-sync status on the Calendars tab, URL rotation strikes after edits. When you connect a new feed, verify it end-to-end once (compare a known booking, ask Rezi about a booked date). And complete the two-way mesh, most “calendar problems” that reach support are actually one-directional setups encountering exactly the double-booking risk the mesh exists to prevent.