tessarin_webhook-timeouts | Stripe Developers | Page 1

charred oarBOT Mar 20, 2025, 10:02 PM

#

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

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

#

obsidian nova Mar 20, 2025, 10:04 PM

#

Hi there. Having a look

random trail Mar 20, 2025, 10:04 PM

#

Thank you. One of the event IDs above is an example of live mode failure, and the other of test mode success — to the same webpoint.

obsidian nova Mar 20, 2025, 10:09 PM

#

So for event evt_1R4qxiEY0XaZ8TR3XRSIv2Xa, it looks like it took about 21 seconds for Stripe to receive a response. Does your webhook handler perform some operations before responding to Stripe?

random trail Mar 20, 2025, 10:11 PM

#

It responds right away, and then stores the received data in a database where another process will catch it up and do the necessary processing. So, 21 seconds is really strange. Check the other event ID, if possible. It was sent to the same endpoint and resulted in a quite immediate response.

#

The only difference I can see between them is the originating IP. I suppose your live mode calls come from a different place from the test mode calls, naturally. But if it was a network problem, I wouldn't even receive the call. Yet I do receive it, normally. This is quite strange.

obsidian nova Mar 20, 2025, 10:14 PM

#

Looking to see if there is anything else we can say from our side, but unfortunately it is difficult to say why we didn't receive a response in a certain timeframe

random trail Mar 20, 2025, 10:15 PM

#

I completely understand.

charred oarBOT Mar 20, 2025, 10:18 PM

#

random trail Mar 20, 2025, 10:18 PM

#

Just to eliminate my logic, I will temporarily make my webhook return 200 and exit without doing anything else. I'll then send a dummy post request from my local machine with curl. And then resend a webhook from Stripe's dashboard. I think the result will be the same, but this should completely eliminate the possibility of the fault being my server "slowness".

olive tusk Mar 20, 2025, 10:24 PM

#

Hi! Jumping in for my colleague. Let me know once that's done so we can see how that turns out!

random trail Mar 20, 2025, 10:27 PM

#

Coming back to publicly display my shame—the issue is on my side.

olive tusk Mar 20, 2025, 10:27 PM

#

I will not accept your shame in public or private. 🤪 Things happen, no worries. 🙂

random trail Mar 20, 2025, 10:29 PM

#

Sorry to bother you all with this! 🤡

I'm off to investigate where in the 15 lines of code the response is being held up, as well as why it works in test mode.

Thank you very much

olive tusk Mar 20, 2025, 10:30 PM

#

Of course! Sometimes it just takes a conversation to figure stuff like this out - and we're always here to help with that. 🙂

#tessarin_webhook-timeouts