Work that runs and finishes.
WHAT A JOB IS
Work that runs to completion, rather than serving continuously.
WHAT EXAMPLES LOOK LIKE
Database migrations Imports and exports Report generation Cleanup tasks
WHAT AN ORCHESTRATOR PROVIDES
Running it, retrying on failure, and recording completion.
WHAT TO SET
How many retries A deadline How long to keep finished jobs
WHY KEEPING THEM MATTERS
Their logs are the record of what happened.
WHY NOT KEEPING THEM FOREVER MATTERS
They accumulate.
WHAT A SCHEDULED JOB IS
One created automatically on a schedule.
WHAT TO DECIDE
What happens when a run overlaps the previous one.
WHAT THE OPTIONS ARE
Allow it Skip the new one Replace the running one
WHAT TO CHOOSE
Skipping, usually.
WHY
Two copies of a migration or import running together is dangerous.
WHAT TO CONSIDER ABOUT MISSED RUNS
Whether the job catches up, or skips.
WHAT TO BUILD INTO THE JOB ITSELF
Idempotency, so a repeat is harmless.
WHY
Retries are automatic, and you will not control them.
WHAT TO MONITOR
Whether each scheduled job ran Whether it succeeded How long it took
WHAT TO ALERT ON
A job that did not run.
