#seb1_webhooks

1 messages ¡ Page 1 of 1 (latest)

proud surgeBOT
#

👋 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/1346950384781885611

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

safe steeple
#

Notice the event id is the same

undone horizon
#

Hello there

#

Taking a look

#

If you don't mind me asking, who is your hosting provider?

safe steeple
#

GCP

undone horizon
#

Gotcha, well I'm seeing that there was a timeout where we didn't receive a response in time from your Webhook endpoint which resulted in the failure

#

Are you doing any other processes in your endpoint before responding to the request?

#

You should respond immediately with a 200 when you receive the webhook request and then handle any other logic afterward.

safe steeple
#

Interesting, we process the request prior to responding. I'm guessing you recommend putting the message in a queue something then proccessing asynchronously?

undone horizon
safe steeple
#

Got it, interesting. Given the fact that the event in both in the success and failure should I assume its good?

undone horizon
#

I'm not sure what you mean by that exactly?

#

But the retry did succeed, yes, so that Event was handled by your endpoint.

safe steeple
#

Sorry what I mean is that the event still currently showing as failed in the dashboard and will retry soon

undone horizon
#

Oh yeah these Events do still retry if you triggered them manually.