#acco
ripe juniper
random ridge
Hello! Can you provide more details? What do you mean by "eventual consistency"?
severe prism
Hey Rubeus!
Essentially: We paginate through the /events endpoint to find out everything that's changed. When many events are created in the same second, we've noticed situations where when we use an ending_before={event_id} from one response to make our next request, it can "skip" over a couple events.
When we re-use that same ending_before={event_id} cursor some time in the future, the events it skipped over are present.
We've been able to find several instances of this with a lot of logging. We're working on a script that can replicate the situation.
Just wrote about it more here, if you want more detail:
https://blog.sequin.io/finding-and-fixing-eventual-consistency-with-stripe-events/
We're pretty certain we're not crazy, but we can't find confirmation anywhere about this behavior.
random ridge
As far as I know the behavior you're describing is not intentional, let me take a look...
severe prism
Ok, thanks 🙏
If you confirm it's not expected, we'll see if we can come up with a script that replicates.
random ridge
No problem. Give me a few minutes.
random ridge
We're going to investigate this further internally, and we do believe the behavior you're seeing is a bug. Thank you for the details and the blog post!
severe prism
Got it, thanks @random ridge ! Looking forward to hearing back
random ridge
The threads and discussions here are short-lived. This will likely take some time for us to investigate, so I can't give you updates later via Discord. If you want to receive updates go to https://support.stripe.com/contact/email and fill out the form to create a support ticket. Provide details about your issue and mention me (Rubeus) in your message. Let me know when you've submitted the form so I can grab your ticket and follow up later.
severe prism
Just submitted, @random ridge !