andypotato
RRunPod
•Created by andypotato on 3/3/2025 in #⚡|serverless
Async workers not running
When using the
/run
endpoint I will receive the usual response:
However the job is never getting processed, despite there being available workers.
Some observations:
- A worker will spin up and go into "running" status, but the rp_handler.py is never executed
- When I check the status of the job via /status/<jobId>
the job will immediately start running
- I can reproduce the exact same behavior using the local test version, so this is not limited to cloud usage
- Running the exact same worker with /runsync
will work without problems
Using the runpod sdk 1.7.7
How can I solve this issue?10 replies
RRunPod
•Created by andypotato on 2/22/2024 in #⚡|serverless
Returning error, but request has status "Completed"
Hello,
I'm using validate() from rp_validator to validate my input data against a schema. The relevant line of code to trigger the error is:
The validation works as expected when using a local test_input.json file. It will pass when all parameters are available, it will result in the job being marked as "Failed" when parameters are missing.
However when running on a serverless instance, the request will be marked as completed, despite the input validation returning an error. The log shows:
This is the response:
Why is this COMPLETED and not FAILED?
Thank you for any hints or pointers.
5 replies