#raimund_webhooks
hard cipherBOT
đ 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/1303424269077839912
đ 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.
- raimund_api, 18 hours ago, 10 messages
- raimund_api, 3 days ago, 43 messages
hybrid parrot
Hello! Events arriving out of order is normal and expected. See here for details: https://docs.stripe.com/webhooks#event-ordering
lyric coyote
I was afraid you might say that. It's just a new phenomenon for us. So the best thing in order to enforce the "correct" order is probably to throw an error on the unexpected one?
hybrid parrot
Do you mean respond to the Event delivery request with a failure status, indicating it wasn't delivered?
hybrid parrot
No, you should not do that.
You should accept the Event and handle the scenario depending on your needs and context. You could store it for later processing. You could fetch the current state of the object from the API. You could queue it until you receive the other Event. Things like that.
lyric coyote
Agreed that's probably the cleanest solution.