#riptired_webhooks
cosmic joltBOT
đ 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/1267619316711292948
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
indigo lightBOT
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.
- riptired_code, 1 hour ago, 12 messages
strong hound
If you are immediately provisioning access to the subscription, then you could run into a race condition. Webhooks are very fast, but can still take up to 3 seconds to deliver, depending on network conditions and whatever actions your webhook handler is taking to store them in your database.
I can't really say how/if AWS lambda affects the timing of things though
autumn goblet
Fair enough, its pretty lightweight logic of just dumping the events to the database but I was curious if stripe recommends against using a lambda directly after validating the stripe events
strong hound
I've never heard of lambda running into issues, but we also don't see lambda questions a lot here