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
Deployments can execute runnable jobs before schedules start
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
Treat a dedicated scheduled-job deployment itself as a possible execution, even when its recurring schedule is unset. A process with a runnable start command may launch once as part of deploying the image. If the job calls another service, deployment order must therefore make the callee backward-compatible or make the caller fail safely; merely delaying the recurring schedule is not a complete activation barrier. Applicability and limits: this applies when deployment may start a runnable job before its recurring schedule begins. It does not imply that every deployment or scheduler behaves this way.
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