Webhook problem
Some requests (about 5%) are not recieved by our webhook. Strange thing is that we recieve updates, but they are with uknown task ids, which we can't find in our DB
10 Replies
did you check the webhook graph?
its on endpoint page
yes, we receive requests, but on 5% we can't find rows related to this task id. is there any way it could be changed?
can you explain what are you seeing for those requests? are they completed but you dont get them? they stay in progress and never complete?
@flash-singh I am also experiencing this issue where some of my webhooks are only firing for
IN_PROGRESS but not COMPLETED after switching over to using webhooks earlier today. Simple requests are working fine, but it seems that there may be some limit on webhook payload size or something which prevents them from firing for COMPLETED status when the payload is large. The payload is fine for /run and /status though, so not sure why it would be an issue for the webhook. I am using webhookV2.
By the way the webhook graph on endpoint page has disappeared for some reason 😦
https://discord.com/channels/912829806415085598/1214853086976282675
I had to revert my deployment where I implemented RunPod webhooks because they are unusable in their current state.I also want to implement webhooks that my app will depend on, but it looks like there are still some issues with them.. hope that these issues can get solved soon before I also implement them in my app for production.
The webhooks are very unstable for
COMPLETED status. I am testing locally on my laptop via ngrok tunnels and the webhook was fired 3 times for COMPLETED status. I am also having my doubts as to whether the payload was too large to prevent the webhook from firing yesterday because as you can see from the Content-Length header, its only a little over 5MB in size.
Actually my apologies, I didn't realise AWS Lambda had a payload size limit of 1MB, so my
COMPLETED webhooks were not firing due to the payload size being too large for Lambda.
However, there is still an issue where the webhooks for COMPLETED are firing 3 times and not just once, as shown in my last screenshot.I was wondering if you still experience issues with webhooks, since I am also planning on implementing those
Seems to be fine, most of the issue was due to user error on my side.
Just sucks that the webhook graphs have disappeared.
they fire 3 times max if request status code is not 200
will check on this