Runpod•10mo ago

Async workers not running

When using the

/run

/run

/run

/run endpoint I will receive the usual response:

{
    "id": "d0e6d88c-8274-4554-bb6a-0a469361ae20-e1",
    "status": "IN_QUEUE"
}

{
    "id": "d0e6d88c-8274-4554-bb6a-0a469361ae20-e1",
    "status": "IN_QUEUE"
}

{
    "id": "d0e6d88c-8274-4554-bb6a-0a469361ae20-e1",
    "status": "IN_QUEUE"
}

{
    "id": "d0e6d88c-8274-4554-bb6a-0a469361ae20-e1",
    "status": "IN_QUEUE"
}

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>
```
/status/<jobId>
```
/status/<jobId>
```
/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
```
/runsync
```
/runsync
```
/runsync
will work without problems

Using the runpod sdk 1.7.7

How can I solve this issue?