#Niladri - subscription

1 messages · Page 1 of 1 (latest)

long token
#

Hi! Can you share the subscription ID (sub_xxx)?

blazing widget
#

Sure

#

sub_1KRpGvKxwZpYBG1DmEadaRyg

#

Event - "evt_1KbzcXKxwZpYBG1Db7GJxTfv"

long token
#

Thanks! Give me a few minutes to look into this.

#

What fields exactly are you looking at in the evt_xxx that you shared?

blazing widget
#

"period": {
"end": 1649645649,
"start": 1646967249
},

long token
#

I think you should look at period_end and period_start instead.

blazing widget
#

Period start and period end is old data

#

It has prev cycle

#

So we had changed our price id in the subscription a few days back for all users

long token
#

Got it! Give me a few minutes to look into this.

blazing widget
#

The only way to reliably see the different events is proration but it's not the most robust way

#

I only want to pick the renewal data

#

Any update?

long token
#

Sorry for the delay, Discord is quite busy this morning. My colleague will come soon to help.

blazing widget
#

Thanks!

#

Please try to help soon, it's affecting our subscription renewals

river escarp
#

yeah that's normal

#

the period on an Invoice is the previous period, it's the period that just completed

#

you shouldn't use that, you should be looking at the period on the Subscription object, that has what you want.

#

so if you have an Invoice object, you should retrieve the Subscription object(referenced by the subscription field on the object) and look at current_period_end on that object, not the Invoice.