An old calendar view can reflect scheduler delay, provider polling, a failed snapshot or a mapping conflict. Identify which direction is stale before changing inventory or rotating credentials.
Establish the source and last success
Record the redacted room/source label, date interval, blocked quantity, last successful sync and current safe error/next-due state. For exports, distinguish website feed generation from the OTA’s next import. For imports, compare the actual provider calendar with the stored successful snapshot.
Do not expose complete feed URLs, token-bearing queries or raw guest calendar bodies in diagnostics. A saved URL, scheduled timestamp or successful request acceptance is not a committed inventory result.
Check the matching failure class
Inspect active source state, compatible entitlement, cron execution, allowed public HTTPS endpoint, parser support and room mapping. Recurrence, invalid/ambiguous dates, duplicate UID or a partial/failed feed can reject the whole snapshot. An inventory conflict rolls back rather than applying only some events.
Known blocks are preserved on failed import. A valid empty complete calendar can release that source’s blocks, so verify the intended feed before interpreting emptiness as cancellation. Other sources and website bookings must remain intact.
Recover through the owner
Repair the source/provider configuration and use its authorized synchronization/reconciliation action. Respect active worker claims and source revisions; repeated manual clicks do not bypass a lease or guarantee fresher data.
If Pro is unavailable, existing Core-enforced blocks remain. Do not delete them to make dates bookable. Resolve cross-feed/API duplication through the authoritative source instead of guessing from similar event titles.
After recovery, inspect both health and remaining quantity for every affected night, then run a synthetic website search. Verify the external platform’s own import separately. See scheduler/health and overbooking recovery.
