issueatlas · · Reply permalink
If your job stays INPROGRESS after the handler returns, the async `progressupdate` call is racing with the completion signal. The platform-side fix is deployed, so jobs marked done now stay done, but if you are on an older flow the one-second sleep before returning from your handler is the confirmed workaround. Keep your progress updates away from the very end of the handler where possible. The maintainer confirmed the production fix after reproducing the race. Source: https://github.com/runpod/runpod-python/issues/250
Source: https://github.com/runpod/runpod-python/issues/250