Black Friday
Skip to documentation content

Channels & Calendar

Monitor iCal scheduling, retry and health

Pro's iCal scheduler processes due active sources using their saved intervals. WordPress cron is best effort: a one-minute scheduler tick does not mean every source synchronizes every minute or at an exact wall-clock time.

Pro’s iCal scheduler processes due active sources using their saved intervals. WordPress cron is best effort: a one-minute scheduler tick does not mean every source synchronizes every minute or at an exact wall-clock time.

Inspect the relevant times

The default source interval is 30 minutes, configurable from 5 to 1,440. The tick starts a bounded batch of up to five due sources with a non-preemptive start budget. A slow in-progress network operation is not forcibly completed by that budget.

Inspect source health for last success, next due, failure count and safe error classification. Last successful inventory remains relevant after an error; a displayed failure must not erase it. Health can report stale, missed or stalled work based on the configured interval and lease state.

Understand retry behavior

Transient failures use bounded exponential backoff with jitter. Configuration/parser failures wait for their longer retry period and usually need operator correction. Busy, changed, inactive or unavailable-feature cases are deferred rather than treated as a successful import.

An interrupted worker has a fenced claim/lease; a later completion must still match the active claim and source revision. Repeated retries do not clear occupancy. Success resets failure state only when health and inventory commit consistently.

Recover deliberately

  1. Check cron execution, source enablement, entitlement, public HTTPS reachability and provider feed validity.
  2. Fix the owning configuration without revealing its URL or changing inventory rows manually.
  3. Use the authorized source synchronization action and inspect both health and the resulting occupancy.
  4. Confirm the site’s operational scheduler is appropriate for its traffic. A system cron can invoke WordPress cron when reliable execution is needed.

Avoid launching many manual retries while an existing worker is active. Do not interpret a pending job, configuration save or scheduled timestamp as provider success.

The retained Booking.com/Agoda API scheduler is separate; iCal health does not certify those integrations. Real external feed delivery and cron timing need their own environment checks. See stale inventory diagnosis.

Was this article helpful?

Your feedback helps us improve the documentation.