Ac Scheduled Jobs

Designing and diagnosing work that runs on a schedule rather than on request: run semantics when a trigger is missed, at-least-once delivery and idempotent job bodies, singleton execution and the lock that prevents overlaps, long-run and overdue jobs, backfill and catch-up after downtime, monitoring liveness versus completion, and the written schedule record. It explains the semantics of time-triggered work; it never recommends a scheduler and never treats silence as success. Use when asking "cron job", "scheduled job", "missed run", "job overlap", "singleton lock", "catch up after downtime", "backfill schedule", "why didn't the 9am job run", "job still running", "at least once job". Not for multi-step durable workflows (ac-durable-execution), not for queue delivery to endpoints you don't own (ac-webhook-and-async-delivery), not for CI pipeline scheduling (ac-ci-and-release).

jiayaoqijia Updated 81 repo stars

File contents

jiayaoqijia/cryptoskill commit d6a7606716

Frequently asked questions

npx get-skill add jiayaoqijia/ac-scheduled-jobs