mtanzi-sub-anchor | Stripe Developers | Page 1

fresh wagon Mar 31, 2022, 5:08 PM

#

hello, reading one sec

#

you're trying to anchor the Subscription beyond its next billing date, which won't work right, you can only update anchor b/w now and the next recurring cycle

little bone Mar 31, 2022, 5:09 PM

#

looking at the data from chargebee the nextbilling date is chargebee_subscription.current_term_end

#

[9] pry(main)> Time.at 1648672876 # current_term_start
=> "2022-03-30T22:41:16.000+02:00"
[10] pry(main)> Time.at 1651351276 # current_term_end
=> "2022-04-30T22:41:16.000+02:00"

#

The data that is in the error is a couple of hour before

Time.at 1651333793
=> "2022-04-30T17:49:53.000+02:00"

#

but I don't know where this date is coming from

fresh wagon Mar 31, 2022, 5:15 PM

#

stepping away, a colleague will be helping out in a bit

little bone Mar 31, 2022, 5:22 PM

#

thanks..

wraith linden Mar 31, 2022, 5:22 PM

#

Hi 👋 I'm stepping in

little bone Mar 31, 2022, 5:22 PM

#

Hi!

wraith linden Mar 31, 2022, 5:25 PM

#

Do you have an ID for this request?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request

little bone Mar 31, 2022, 5:26 PM

#

let me check... one sec

#

req_N5jkjJqVGsfq3p

wraith linden Mar 31, 2022, 5:37 PM

#

So it appears to me that the back-dated start date combined with the per month price is creating a situation where the next billing cycle will start sooner than you want to set the billing cycle anchor. This is where the 1651333793 is coming from. Given how close they are I suspect there may be some rounding issue with the timestamps

little bone Mar 31, 2022, 5:38 PM

#

mm that's around 5 hours

#

the thing is only some of the subscriptions are failing with this issue

#

and the data I pass is just take from chargebee and used in stripe... I am assuming is correct

#

what would you suggest I should do to solve this issue?

wraith linden Mar 31, 2022, 5:43 PM

#

Well for starters we do not recommend recurring monthly billing at the end of the month. When February comes around it will move the date to the 28th and leave it there. The 1st of the month is a better option in general.

#

My second question is why you need to update the billing cycle anchor to a new date if it already is basically a match for when the next billing cycle will start

little bone Mar 31, 2022, 5:44 PM

#

one interesting thing is that the time sent by stripe (1651333793) is exactly 1month from the time I run the migration

wraith linden Mar 31, 2022, 5:44 PM

#

run the migration
What do you mean by that?

little bone Mar 31, 2022, 5:46 PM

#

no nevermind..

#

the migration run today at "2022-03-31T15:49:52.50Z"

#

Well for starters we do not recommend recurring monthly billing at the end of the month.

we don't do at the end of the month... it happen by chance that now was at the end

wraith linden Mar 31, 2022, 5:47 PM

#

Okay

little bone Mar 31, 2022, 5:47 PM

#

we just take the data from chargebee and put into stripe 🙂

#

the monthly it's calculated depending on the product

wraith linden Mar 31, 2022, 6:10 PM

#

Okay so it appears there is a 5 hour gap between when the next billing cycle will occur and when you are trying to set the billing cycle anchor, you are trying to replicate the identical data as is currently in Chargebee and this conflict is preventing that. Do I have that correct?

little bone Mar 31, 2022, 6:11 PM

#

yes

#

that's the issue

wraith linden Mar 31, 2022, 6:20 PM

#

Okay .... Hmmmm

dusty pecan Mar 31, 2022, 7:34 PM

#

Hi there 👋 apologies for the delay here, just wanted to confirm that you're still struggling with this?

#mtanzi-sub-anchor