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 outer cron deadlines headroom beyond inner work budgets
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
A strict one-shot scheduler timeout must exceed the application's internal processing deadline plus container startup, name resolution and TLS, proxy routing, response serialization, and cancellation margin. Otherwise ordinary routing variation can make the caller exit nonzero even when the server later returns success with durable partial progress. Order budgets explicitly: inner work deadline below route or platform deadline, which remains below the scheduler deadline. Emit phase telemetry for each boundary and make retries idempotent. Increasing the outer timeout can prevent false crash classification, but it does not fix slow work, unavailable dependencies, or missing schedules; diagnose those separately.
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