Repository navigation
docs: clarify serverless worker lifecycle and what Idle means - #895
Merged
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
justinwlin
marked this pull request as ready for review
October 14, 2026 05:01
…timeout The console's Idle state means a scaled-down, unbilled worker, while the idle timeout is a running, billed worker waiting for its next job. Docs used 'idle' for both. Add a lifecycle diagram, align state, cold start, delay time and billing wording across Serverless and Flash pages.
justinwlin
force-pushed
the
docs/serverless-worker-lifecycle
branch
from
October 15, 2026 18:32
34e0ccd to
997f604
Compare
lavanya-gunreddi
approved these changes
Oct 15, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The docs used "idle" for two opposite things:
This PR keeps "Idle" for the console state only and calls the idle-timeout window waiting.
Changes
serverless/workers/overview.mdx: new Worker lifecycle section with a state diagram (scaled down vs running, and which part is billed). Rewritten states table. Outdated is described as a version-column tag, not a state.Source of truth (code)
desiredStatusisRUNNING, from resume to stop:runpod-backend/node/podBillingWorker/helper.ts:120-142.StopPod:ai-api/pkg/api/jobTake.go:356-366,413-449./healthusesidle/readyfor EXITED pods with a cached image:ai-api/pkg/api/health.go:76-120.desiredStatus === "RUNNING"and Idle when the pod is stopped and ready:main-ui/console/src/features/Serverless/Endpoint/WorkerWidget.tsx:47-67.host/pkg/syncimages/images.go:158-305.