#Nick-subscription-update
1 messages ยท Page 1 of 1 (latest)
Thanks!
To add a little more context, the latter case is how it's been working for a long time, so I'm surprised to see the former react that way
Appreciate your patience, server is running a little busy today.
looking
No worries ๐
Hi ๐ I'm stepping in to take a look at the weirdness
Okay so I've only looked at the events but the first event shows that billing_cycle_anchor, current_period_end, and current_period_start were among the properties to be changed in the update, where as in the second event these properties were not changed
Is that unexpected?
Sorry, I think I linked the incorrect second event. Here's the correct second event (original message updated): https://dashboard.stripe.com/events/evt_1LAOQjI67GP2qpb4LNwJ4QLv
If you compare the actual POST requests that triggered the events, they're basically the same, but one of them resulted in billing_cycle_anchor changing, and the other didn't
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
FWIW, neither requests modify the billing_cycle_anchor or the other fields explicitly, just adding a subscription item
Sorry it's been busy. My first hunch is it's something specific to the price. Looking now
Okay, I think the reason the second API request didn't change these fields is that the second price is for $0.
Looking more
Okay so for the first request you changed the price associated with the subscription from a $0 price to one that had a unit_amount