Catch-up Policy

The Problem

When a worker goes offline or your webhook endpoint is down, scheduled executions are missed. When the system recovers, what should happen?

Catch-up Modes

Set the catch_up field when creating or updating a cue:

run_once_if_missed (default)

If any windows were missed, create exactly one execution, then resume the normal schedule. Safe default: prevents storms.

{"catch_up": "run_once_if_missed"}

skip_missed

Skip all missed windows. Advance the schedule to the next future window. No backfill executions created.

{"catch_up": "skip_missed"}

Best for: status checks, dashboards, anything where old data is stale.

replay_all_missed

Create an execution for every missed window. Capped at 100 to prevent runaway. Use carefully.

{"catch_up": "replay_all_missed"}

Best for: billing, compliance, audit trails where every window matters.

Example

curl -X POST https://api.cueapi.ai/v1/cues \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "daily-report",
    "schedule": {"type": "recurring", "cron": "0 9 * * *"},
    "callback": {"url": "https://example.com/webhook"},
    "catch_up": "skip_missed"
  }'