iCal synchronization is periodic and best effort, not real time. The scheduler ticks every minute and processes due active sources in bounded batches. A source defaults to a 30-minute interval; its configured interval may be 5 to 1,440 minutes. A real cron runner is recommended for sites where WordPress traffic is low.
Read health
On the room’s OTA Sync tab, inspect Last success, Last attempt, Next scheduled attempt, Recent runs (up to 10) and Last sync reason. The useful states are:
- Healthy: the last snapshot committed successfully.
- Awaiting first sync or updated settings: no successful snapshot yet.
- Sync in progress: another worker owns the lease.
- Retry scheduled: a transient failure will be retried.
- Overdue — check cron or Worker interrupted: the source needs attention.
- Sync failed: configuration or parser data must be corrected.
Transient errors retry with bounded exponential backoff and deterministic jitter. Configuration and parser failures retry later but never clear occupied blocks. The health overview uses an allowlisted reason, not raw exceptions, feed URLs or guest data. Logs are retained for up to 100 runs per source and 30 days.
If a source is stale, verify cron delivery, public HTTPS, the masked URL and the OTA calendar itself, then select Sync now once. A successful empty feed releases only that source’s blocks. A fetch, parse, license or storage failure preserves the last known good snapshot. Do not mark dates available manually.