ab92023_webhooks

[manic mortar]

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

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

[wary merlin]

Further sample events: evt_3PxqYsAMTZO1JfZx0HBDqkRM, evt_3PxqXvAMTZO1JfZx01yGk2zY, evt_3PxqVWAMTZO1JfZx0dfFZTGu

[muted sonnet]

Let me take a look

For the first event evt_3PxpqCAMTZO1JfZx204Vc6Bt you shared with an api.xxxx.co.uk endpoint address, I ran an MTR report and I'm seeing some packet loss on one of the IPs of your server

You can share that with your hosting provider so that they can fix the issue

looking at other events

Same with an pay.xxx.su endpoint

Let me know if that helps @wary merlin

[wary merlin]

It appears to be an AWS routing issue. We're proxied behind Cloudflare, which is the step 8 address, so this would be the in-transit between Stripe / Cloudflare, before it even hits our infrastructure / network

[muted sonnet]

Ah yup, that'd make sense

[wary merlin]

Is there a difference when a webhook re-attempt is made in the dashboard versus a webhook fired during an action? This is starting to have a fairly large impact on our operation.

[muted sonnet]

Difference in what sense? Retried events deliver the exact same copy of payload if that's what you're asking

[wary merlin]

Network routing or similar - all your requests appear to be coming from a US data centre.