Search
Star
Feedback
Setup for Free
© 2026 Hedgehog Software, LLC
Twitter
GitHub
Discord
System
Light
Dark
More
Communities
Docs
About
Terms
Privacy
Worker terminated mid-job - retried 5 hours later. - Runpod
R
Runpod
•
2w ago
•
38 replies
Elif Sezgin
Worker terminated mid-job - retried 5 hours later.
Curious about Flex worker behavior
. Do serverless Flex workers ever get terminated mid
-job
(e
.g
.
, SIGTERM
) to prioritize capacity for On
-Demand Pods or Active workers during tight GPU demand
? If so
, what
's the best way to monitor when this happens
?
Runpod
Join
We're a community of enthusiasts, engineers, and enterprises, all sharing insights on AI, Machine Learning and GPUs!
21,202
Members
View on Discord
Resources
ModelContextProtocol
ModelContextProtocol
MCP Server
Recent Announcements
Similar Threads
Was this page helpful?
Yes
No
Similar Threads
Worker not executing job
R
Runpod / ⚡|serverless
14mo ago
Job Stuck in Queue Eventhough worker is ready
R
Runpod / ⚡|serverless
12mo ago
Worker keeps running after finishing job, burning money?
R
Runpod / ⚡|serverless
16mo ago
Stuck IN_PROGRESS but job completed and worker exited
R
Runpod / ⚡|serverless
17mo ago