Runpod return {'error': 'request does not exist'}
I'm using stable-diffusion-forge template. I have sent requests to runpod using /run endpoint and /status endpoint for retrieving the status. Everything work normally until today when im checking the error log, it shows {'error': 'request does not exist'} when sending the /status. I think the error above is from runpod webserver. Can anyone explain about this?
Solution:Jump to solution
If you use
/runsync your request status expires in 60 seconds, and if you use /run, it expires in 30 minutes, so you need to retrieve the status before it expires. I also think you're confusing pods with serverless, because you don't use a stable-diffusion-forge template in severless, you are probably using some custom one.10 Replies
Solution
If you use
/runsync your request status expires in 60 seconds, and if you use /run, it expires in 30 minutes, so you need to retrieve the status before it expires. I also think you're confusing pods with serverless, because you don't use a stable-diffusion-forge template in severless, you are probably using some custom one.Yes, i'm using a custom one from ashleykleynhans but i dont think the problem is from forge. So when the request is expired, it will return above error? But i'm using the /run and try to retrieve the result immediately, weird
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
Yes, that what im doing now, everything working right but only one request return that error
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
Yes, everything is good now but i want to understand why it happened to handle that in the future
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
How are you sending and checking the request? If you're using postman, ensure the request id is correct.
Thanks,
I'm using runpod sdk
i dont thing the request id is wrong because every others request work normally
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View