#river-event-created

1 messages · Page 1 of 1 (latest)

mortal flowerBOT
hollow steeple
#

@upbeat sundial not if both requests happen at the same second for example. But overall no, no guarantee there at all

#

river-event-created

mortal flowerBOT
upbeat sundial
#

Apologies for the delayed response. Even if the requests don't happpen at the same second?

If you're still around, the particular usecase I'm looking at is:

  1. User cancels subscription by setting cancel_at_period_end: true.
  2. Couple seconds later they "uncancel" by setting cancel_at_period_end: false.

This will generate 2 events / webhooks. I understand that the webhooks could be delivered in any order, but are you saying that the event created from 2 could potentially have a created timestamp that's <= than the created timestamp from event 1?

#

I guess the better question might be if I make a Subscription update API call, is there a guarantee that the event gets created before we get a success response back from Stripe?

umbral igloo
#

heya! taking over from koopajah, let me get back to you in a bit

upbeat sundial
#

Hi thank you! I think the way I phrased the initial question was confusing. You can ignore everything in this thread. My updated question is below:

If I make a Subscription update API call, is there a guarantee that the Stripe Event object gets created before we get a success response back from Stripe? Or is the event creation in your system asynchronous such that it's possible that the Event could get created say 5 minutes from now. (note I'm referring specifically to when the Event is created, not when the webhook is delivered)

umbral igloo
#

I would say that there's never any guarantee about the time the Stripe Event object would be delivered. A lot of this depends on network conditions and processing time.

My recommendation in this case would be to simply retrieve the object again when you get an event to ensure you always have the latest object state if that's important to you

upbeat sundial
#

Ok thank you!!