diff --git a/serverless/troubleshooting.mdx b/serverless/troubleshooting.mdx
index 402f5cb56..864d10359 100644
--- a/serverless/troubleshooting.mdx
+++ b/serverless/troubleshooting.mdx
@@ -39,7 +39,7 @@ If jobs remain `IN_QUEUE` for extended periods:
 
 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.
+Versions 1.7.11 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: