#GastonLifschitz
dapper warren
fast roost
Unfortunately webhook order can't be depended on so we recommend coding your event reactions in such a way that you can receive them in any order.
This mostly comes down to network variability when Stripe sends you events but there are also instances when Stripe will create multiple events at once and some can get sent out at slightly different times than each other.
lofty oriole
I get it, but can it be sent on your side in a more ordered manner? Because it makes more sense for a trial to end and then start a new subscription that the other way around. I think order here is key
fast roost
Unfortunately not. We would need to wait for you to confirm each event before sending the next one and at the moment we don't offer that functionality. I can put in a feature request but I can't promise that that would get added any time soon
So in this case we would basically encourage your server to have logic that understands that a subscription cycling would indicate that the trial has ended even if you haven't gotten that event yet
I understand the utility of events being ordered, we just unfortunately don't offer that at the moment
lofty oriole
Totally understand, but I have an issue here. A new subscription that's purchased is being cancelled on Stripe's end. So the new subscription is bought and automatically after that gets cancelled. On our end this subscription is active but on Stripe it gets canceled. Any solution to that?
karmic moss
Hello 👋
Taking over as Pompey had to step away
The only alternative that I can think of is to poll the API to retrieve the subscription status
lofty oriole
Mmmm, the thing is that the subscription should be active, on our end is active and Stripe is canceled because of the order that things went (despite of the webhooks). I wouldn't like to active a subscription twice because of bad ordering if that makes any sense
And hey Hanzo!
karmic moss
Sorry, can you expand a bit more on how the subscription is getting cancelled on Stripe?
lofty oriole
For instance let's take the following example (actual user). This user had a trial and after that the subscription was purchased for the actual one and after that it got immediately canceled
sub_1LjRjpI2QiYH8V4plyapuIZx
For you to check
karmic moss
It was cancelled because your server sent a request to cancel the subscription
https://dashboard.stripe.com/logs/req_a5gJDNzZtujRmZ
you'd need to configure some logic on your server to only call this cancel endpoint under certain conditions
lofty oriole
Oh i thought this was send by stripe. Then it was our fault. Sorry for that, I assume it was from Stripe since the source is
Stripe/v1 NodeBindings/8.112.0
leaden ginkgo
Hi 👋
@karmic moss had to step away. That source string is the Stripe client library used by your server.
leaden ginkgo
👍 after you look into it feel free to come back if you have more questions
lofty oriole
thanks guys!!