#osnet_webhooks

1 messages · Page 1 of 1 (latest)

red sedgeBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1368806854972538904

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

sweet gyro
#

We have been experiencing too many webhook failures since yesterday.

unborn spade
#

Hi there, based on the webhook log, the webhook wasn't delivered to your endpoint due to a timeout problem. Meaning your webhook server took too long to provide a response.

sweet gyro
#

We had never encountered this issue before yesterday. I’ve checked our service, and it appears to be working fine.

unborn spade
#

Have you audited your server log?

#

And check the logs around the time when the timeout error happens, i.e., 2025-05-05 01:50:25 UTC

sweet gyro
#

Yes no issue was found

unborn spade
#

Ok, then you'll want to work with your hosting provider and see if they experience any service downtime during that time.

sweet gyro
#

For example, we don't process any logic for this event and return immediately. However, as you can see, this event still fails even though other events are working fine.