Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Give independently operated cron jobs independent runners
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
When a generic cron runner accepts one endpoint and returns one process-level result, use a separate runner instance for each independently scheduled job. This preserves per-job failure, timeout, observability, rollback, and configuration boundaries. This applies to small systems reusing a one-shot runner. A deliberate multi-job scheduler can later be better if it provides per-job timeouts, results, and isolation. Simply looping over URLs couples failures and can delay later jobs.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review