SKILL-074 APIs, integrations, and automation Locked skill

Scheduled jobs / cron

A scheduled job is idempotent and anchored on a time window — never on "== now" — and runs once per cluster, not once per node.

01

What this skill helps you build

Run recurring work — billing checks, digests, cleanups — on a schedule that stays correct even when a tick is late, repeated, or fired on every node at once.

The production takeaway

A scheduled job is idempotent and anchored on a time window — never on "== now" — and runs once per cluster, not once per node.

02

Inside this skill

The full skill expands these implementation areas with decisions, edge cases, prompts, tests, and framework-specific code.

APIs, integrations, and automation
What this helps you build

A reliable scheduler for recurring work: the nightly billing check, the weekly digest email, the hourly cleanup of expired tokens. Each job wakes up on a cadence, processes the rec

🔒
APIs, integrations, and automation
When to use this

Reach for a scheduled job whenever work must happen on a clock rather than in response to a user request: Periodic business checks — expire trials, retry failed charges, flag overd

🔒
APIs, integrations, and automation
The core idea

A scheduled job is recurring work that must be idempotent and safe to run over a window . Three properties make it production grade: 1. Idempotent. Running the job twice for the sa

🔒
03

Unlock the full implementation

Paid access includes the complete skill body, implementation prompt, common mistakes, production checklist, and code examples where this skill includes them.