#wiiim

1 messages · Page 1 of 1 (latest)

rotund ospreyBOT
elfin trench
#

what's the question?

lean cobalt
#

We had many webhook events yesterday and we think that our Network layer thought that stripe is attacking us with a ddos. Therefore 70-80% of the webhooks could not be delivered. The retry mechanism does not work very well in this case, because the whole wave of events is then sent at the same time again which causes our network layer to deny some requests. Sadly we don't know what the issue is there yet.

Is there a way to re-trigger them manually via the api? We saw that this is possible in the dashboard, but when executing something like this: POST https://api.stripe.com/v1/events/evt_1NDzJtBedPgr0Zv29EwPj5Kt/retry, we get You can only retry Events in test mode

elfin trench
#

I don't think you can programmatically retry in livemode

lean cobalt
#

so you mean to download them and send them manually to the webhook endpoint?

elfin trench
#

or just execute the code your webhook handler calls, directly from a script calling those APIs, for instance

rotund ospreyBOT
lean cobalt
#

Hmm, I have another idea. We've found out that the stripe cli is able to retry the event. My idea is now to download the events and run a script which retries the events. Is there anything wrong about that? We can't easily hack that into our code in production right now.

weary briar
lean cobalt
#

Okay, then we'll work with that. One last question: When I retry an event with the CLI and there is a planned retry by stripe (e.g. in 2 hours), this will be canceled then if the manual retry via the CLI is sucessful right?

weary briar
#

One last question: When I retry an event with the CLI and there is a planned retry by stripe (e.g. in 2 hours), this will be canceled then if the manual retry via the CLI is sucessful right?
I'm not sure honestly, you can do a quick test for that, but in all cases you integration should be able to handle duplicate events:
https://stripe.com/docs/webhooks/best-practices#duplicate-events

lean cobalt
#

Alright, thank you 🙂