newt_event-created | Stripe Developers | Page 1

inland hornetBOT Mar 15, 2024, 6:02 PM

#

👋 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/1218258024175636630

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

thin raftBOT Mar 15, 2024, 6:03 PM

#

round bolt Mar 15, 2024, 6:03 PM

#

Hi @fair mason

fair mason Mar 15, 2024, 6:03 PM

#

newt_event-created

#

Hello! You can use created but you need to take into account that it's granular up to the second so it's possible for multiple Events to happen at the exact same second and that wouldn't give you the right order

round bolt Mar 15, 2024, 6:04 PM

#

That makes sense

#

so unless they happen within the same second, we can rely on those

#

Is that correct?

fair mason Mar 15, 2024, 6:08 PM

#

I would say"mostly yes". Events are generated "asynchronously" in our systems so if you did two requests in quick successions I can see a world where two *.updated Events change different part of the Event and one is created/sent faster.

#newt_event-created