#brandan_webhooks
1 messages ยท Page 1 of 1 (latest)
๐ 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/1463206968549445651
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- brandan_best-practices, 6 days ago, 53 messages
hi there, I'm not sure I understand your question. Stripe will automatically retry webhook events that fail for 3 days, see the following guide https://docs.stripe.com/webhooks/process-undelivered-events
are you trying to track when a webhook event is retried?
correct, so by looking at the stripe dashboard is there a good way to see high level for our connect accounts which payment intents have had a webhook attempt for 3 days and they were unsuccessful?
We are trying to figure out IF we get to the point of a webhook failed for 3 days, what do we do and what are the best practices for that?
Within here: https://docs.stripe.com/webhooks/process-undelivered-events?lang=dotnet#process-events
It looks like this is what we'd want to do correct?
we're not super familiar with the dashboard in this channel (we focus on the API and code-related questions) but I don't believe this is a view that exists
Is that possible with .NET api or only with the ones shown in the docs? Ruby/Python/PHP/Node.js
No worries, I think doing a call to the list events api would be sufficent for our case
and yes that is our guide on how to handle undelivered events, or speed up processing ones that are in the retry queue
Okay, and we can 'retry' those unprocessed events even after the stripe auto retry period of 3 days?
yes, by listing the events using the API and processing them, you would just want to make sure to do it within the 30 day retention window
Okay, sounds good. To follow up quick on this question Is that possible with .NET api or only with the ones shown in the docs? Ruby/Python/PHP/Node.js The stripe docs for processing undelivered webhook events - is that possible via the .NET api?
Hi there! Taking over for denton here
The "Process the events" section describes a general recommended approach to processing the events and doesn't rely on any SDK methods - it is just regular code/logic
I don't know much about .NET but you should be able to do the same thing there
Okay, so when we pull the list of those events that failed, when we get those we aren't actually telling Stripe to re-attempt that webhook we should within our system manually handle the event as if we received the webhook from stripe? Is that correct?
When I initally looked at the docs for processing failed events it almost looked like we'd get the list of ones that failed and then ask stripe to re-process the event
Yes, processing undelivered events means your application is handling them as if receiving them from Stripe.
Because Stripe doesn't process events - we send them to your webhook endpoint and track whether you received them or not. If you return a 200 that's the end of it
Okay, sounds good. That clears up my questions! I'll reach back out if I have any more - appreciate it! ๐
No problem! Have a nice day