CloudHub 1 Scheduler Triggering with Latency (Best-Effort Scheduling)

Symptoms

• Scheduler configured with a fixed interval or cron (e.g., every 10 seconds) runs inconsistently
• Observed trigger intervals are longer than configured (e.g., 13s, 16s, 17s, or 20s+)
• Issue is most noticeable at short (sub-minute) intervals

Root Cause

CloudHub 1.0 schedulers operate on a best-effort basis, not at an exact time.
The platform checks for due schedules on a recurring internal cycle. This means:

• Actual run times can drift from the configured interval
• A small absolute delay becomes a large relative delay at short intervals — for example, a few seconds of drift on a 10-second schedule represents 30–50% variance

This applies to both cron and fixed-interval scheduler types.

Resolution

This is expected behaviour of the CloudHub 1.0 scheduler — it is functioning as designed.
The CH1 scheduler does not guarantee exact-time execution. On-platform scheduling is best-effort, and timing variance is an inherent characteristic of the platform, not a defect in the customer's application.

Recommendations

Avoid sub-minute schedules where exact timing is critical. An interval of 60 seconds or more is significantly more reliable, though some variance can still occur.