Help Center/ CodeArts Agent/ FAQs/ Tool Environment and Performance/ What Is the Scheduled Task Jitter Mechanism?
Updated on 2026-07-29 GMT+08:00
View PDF
Share

What Is the Scheduled Task Jitter Mechanism?

Recurring Task Jitter

Each time a recurring task is triggered, it is delayed by a random period of time from the scheduled time.

  • Offset calculation: deterministic calculation based on the task ID (the offset remains identical for the same task across executions and does not change over time)
  • Offset range: min(10% × Execution period, 5 minutes), that is, a maximum of 5 minutes
  • Offset direction: only delayed, not executed in advance

One-Time Task Jitter

The top and half of the hour are the moments when multiple tasks are most likely to be triggered simultaneously. The jitter mechanism is specifically designed to distribute the load during these times. For a one-time task, jitter is added only when the triggering time is exactly on the hour (:00) or half-hour (:30).

  • Offset direction: executed in advance (negative jitter)
  • Offset range: 0 to 30 seconds, meaning that the task can be triggered up to 30 seconds in advance
  • Triggering condition: applied only when the minute is 0 or 30

Deterministic Characteristics of Jitter

The jitter offset is deterministically calculated using the hash algorithm based on the task ID and has the following characteristics:

  • Consistency for the same task: The offset for triggering the same task remains the same each time, ensuring consistent timing.
  • Different offsets for different tasks: Even if different tasks are set with the same period, their offsets are different to prevent simultaneous triggering.
  • Manual configuration not allowed: Jitter parameters are preset by the system and cannot be manually adjusted by users.
Parent Topic: Tool Environment and Performance