#special-schedule-testclocks

1 messages · Page 1 of 1 (latest)

sharp reefBOT
safe glen
#

I was expecting the scheduled_subscription.updated event to be called with a new current_phase when the schedule moved into the new phase, but it wasn't called.

This subscriber did get put on the new price, but that event was never fired.

near bear
#

I don't think that event fires unless the actual Subscription Schedule object changes state.

safe glen
#

Hmmm, I thought that was the right one. We effectively need a way to keep our records up to date when the subscription changes. I looked at the docs and it seems like that would be the right one and we are seeing that event fired in prod for our users, let me see if I can find an example

#

This event was fired and it has the correct current_phase that the subscription is now in.

near bear
#

Ah, maybe you're right. That's odd.

#

What's the Subscription ID for the one that didn't have the scheduled_subscription.updated event?

safe glen
#

This is the subscription_id: sub_1Lpb7rHMtOGkm4dBtAIOlllE!

near bear
safe glen
#

That event is the one for the start of the subscription schedule. It's current_phase field is the first phase (starting subscription), and not the subscription that was updated to

#

The account is currently in a state where the active subscription is the one from the 2nd phase. It updated to the new subscription properly, but I just didn't see that event come in.

#

I feel like I must be doing something wrong but not sure what yet

#

I am going to be away for the most of the day, I can check back in here later if anyone finds anything, but will also keep testing on my end

near bear
#

When you come back, can you look into the logs for that subscription and tell me if customer.subscription.updated has the information you're looking for? If not, I think it might be more helpful if I understood exactly what you need the scheduled_subscription.updated for