From bbe69b7d4a537f3326354fc31a89d16088231a35 Mon Sep 17 00:00:00 2001 From: "promptless[bot]" Date: Wed, 8 Jul 2026 06:52:24 +0000 Subject: [PATCH] Add troubleshooting entry for jobs funneled to a single worker (SDK 1.10.1 fix) --- serverless/troubleshooting.mdx | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/serverless/troubleshooting.mdx b/serverless/troubleshooting.mdx index 0956bf66..90b6403b 100644 --- a/serverless/troubleshooting.mdx +++ b/serverless/troubleshooting.mdx @@ -35,6 +35,20 @@ If jobs remain `IN_QUEUE` for extended periods: - **Workers throttled**: Your endpoint may be hitting rate limits. Check the Workers tab for throttled workers. - **Cold start delays**: First requests after idle periods require worker initialization. Consider increasing `min_workers` or enabling [FlashBoot](/serverless/endpoints/endpoint-configurations#flashboot). +### Jobs funneled to a single worker + +If your endpoint has multiple workers but nearly all jobs run on one worker while the others sit idle, and jobs stay `IN_QUEUE` even though workers are available, you may be running an affected version of the Runpod Python SDK. + +Versions 1.9.1 through 1.10.0 could corrupt per-worker job tracking on endpoints that use a network volume, causing most workers to stop pulling new jobs. This most often appeared on network volume endpoints such as ComfyUI workers. + +To fix this, upgrade the Runpod Python SDK to version 1.10.1 or later: + +```bash +pip install --upgrade "runpod>=1.10.1" +``` + +Then rebuild and redeploy your worker image so the fix takes effect. No configuration or code changes are required. + ### Jobs timing out | Cause | Solution |