Scheduler and warm-up
The scheduler separates request-path work from durable background tasks. Apalis storage owns delayed jobs, claims, retry state, and idempotency keys. Workers on each replica can claim work from the shared store.
Important jobs
Section titled “Important jobs”UpstreamWarmupJobkeeps eligible OAuth upstream windows active.OAuthRefreshJobrefreshes credentials that need renewal.CacheKeepaliveJobruns generation-fenced prompt-cache probes.- Usage rollups, pruning, and metadata refresh jobs maintain operational state.
Warm-up is enabled by default for OAuth upstreams after credentials exist. It does not apply to API-key upstreams.
Retry classes
Section titled “Retry classes”| Class | Use | Attempts |
|---|---|---|
| Probe | Lightweight connectivity checks | 3 |
| Entity | External work such as warm-up or refresh | 5 |
| Maintenance | Internal cleanup and rollups | 1 |
Cache keepalive uses one attempt. Misses, stale generations, decrypt failures, unsupported providers, and dispatch errors are business outcomes recorded in metrics.
Failure triage
Section titled “Failure triage”Terminal jobs remain visible in the scheduler failure view. Inspect the job type, status, bounded reason, and attempt count. Resolve the underlying credential, storage, or configuration problem, then let the relevant watchdog enqueue a new idempotency key.
Failure summaries redact prompts, authorization headers, API keys, ciphertext, and payload-shaped material.