#loterak
1 messages · Page 1 of 1 (latest)
I believe that this will also trigger a subscription_schedule.updated event though I am not 100% sure https://stripe.com/docs/api/events/types#event_types-subscription_schedule.updated
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
I'd reccommend testing this with a test clock to check https://stripe.com/docs/billing/testing/test-clocks
Also I think you can check the request property on the event to see if the update came from the API or from an automatic transition. https://stripe.com/docs/api/events/object#event_object-request-id
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
I'll give it anotehr shot, tested it a while ago and I think it did not trigger. Great that test clocks were added btw, incredible addition
Yes they are a lifesaver
Would you be able to test this again quickly? If it doesn't trigger, I think the thing to do would be to listen to customer.subscription.updated like you said and then to retrieve the schedule and check if you just passed the timestamp between the first two phases
testing it right now!
It really doesn't seem to be the case sadly. I'll use customer.subscription.updated but it would be a great addition to schedules to either use the update event or a more specific transition event for those cases.
Darn, thank you for checking. Will add feedback, definitely agree an event like that would be useful.