Min.K

[outer rock]

Hello! We'll be with you shortly. 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.

• Min.K, 52 minutes ago, 6 messages
• Min.K, 14 hours ago, 17 messages
• Min.K, 21 hours ago, 46 messages
• Min.K, 2 days ago, 17 messages

[latent hedge]

1. I think so, but feel free to test in Test Mode
2. It should be reverse-chronological order, and please test it out
3. How are you retrying? Have you tried resend? https://stripe.com/docs/cli/events/resend
4. It's totally depended on your business logic. Yes using List Stripe Events could work, but it eats up your rate limit (because it's API) and it's not realtime like webhook. On webhook you can look at the events created as it will returns at the same object in List Stripe Events

[long violet]

In order to distinguish that it is the same event during retry, can I use the idempotency_key in the webhook event body?

"request": {
"id": "req_GTUHlaXYjycgaw",
"idempotency_key": "d68fc6a4-972c-48d6-af54-3388a4611e80"
},

or should i use event id? (evt_~~)

[latent hedge]

Could you elaborate how are you retrying? What exact API are you calling?

[long violet]

Resend button

or Automatic retry by stripe

[latent hedge]

That doesn't generate new event. It will send the exactly same event again