Cloudbeds Dual-Write and Rentals

If your account has Cloudbeds connected (in Partners → Connectors), reservations sync into HiLucy on a 15-minute cron. Since April 14, 2026, that sync runs in dual-write mode — and the result is two databases that need to stay aligned. Here's what that means for you.

What syncs

Every 15 minutes, the cron hilucy_cloudbeds_cron_sync:

Pulls reservation changes from Cloudbeds since the last successful sync
Upserts the legacy wp_guest_checkin table (HiLucy's original storage)
Dual-writes the same data to wp_reservations + wp_reservation_guests (the new canonical schema)

The cron only logs when something actually changed — no news is good news.

Which is authoritative

As of April 14, 2026, wp_reservations is the canonical source for reservations. The Rental Manager reads from it. wp_guest_checkin exists for backward compatibility with code that hasn't migrated yet.

The dashboard you see in the Rentals tab is reading the canonical schema — so if you see a discrepancy with what's in Cloudbeds, the canonical schema is what HiLucy "thinks" is true.

When things drift

Two databases occasionally drift out of sync — usually because:

A network glitch interrupted the cron mid-sync
A guest was deleted in Cloudbeds but not propagated yet
A manual reservation was created in Cloudbeds and the cron hasn't caught up

The next 15-minute cron tick reconciles. If something looks off, wait 15 minutes and refresh.

If it's still off after multiple cycles, contact HiLucy support — they can manually trigger a full re-sync.

What you'll notice in Rental Manager

Cloudbeds-sourced reservations show up in the Rentals tab automatically — you don't need to create them manually
Listing IDs match Cloudbeds property IDs (e.g. KAN Tulum = listing 14216 = Cloudbeds property 313946)
Custom fields that Cloudbeds doesn't have (e.g. condition logs, deposits, charges) are stored in HiLucy and aren't pushed back to Cloudbeds

What NOT to do

❌ Don't create a manual rental in HiLucy for a reservation that's already in Cloudbeds — wait for the cron, or use the Acuity / activity flow for non-room bookings
❌ Don't edit the Cloudbeds reservation directly through the Cloudbeds UI for fields HiLucy owns (condition, deposit, charges) — they won't sync back
❌ Don't disconnect the Cloudbeds connector during business hours unless you've coordinated with the team — in-flight sync data could get stranded

Manual sync

If you absolutely need to force a sync (e.g. a Cloudbeds reservation just created and you can't wait 15 minutes), an admin can run:

ssh proxmox "pct exec 120 -- bash -c 'cd /var/www/wordpress && sudo -u www-data wp eval \"hilucy_cloudbeds_sync_reservations(true);\"'"

(Replace 120 with your environment's container number.)

Categories

Language