#reduce_subscription-period
fluid frigateBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1432745196474601574
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
sturdy ruin
hi there, taking a look at this now
hollow sage
thanks
sturdy ruin
it looks like that subscription had a subscription schedule on it that released on the 31st. that caused the billing cycle anchor on the subscription to be set to the 31st
hollow sage
hmm okay but why next billing cycle wasn't calculated as 30 of sept ? instead 1st of oct
and why next billing cycle is set to 30 days instead of 1 full month? 🤔
as I can see in api response it should be full month
sturdy ruin
still looking, one moment while I reach out to my colleagues
hollow sage
okay
Hey Im sorry but i Have 10 more minutes and i need to go, is there any change we can find solution now or We can continue this thread tomorrow or You will write solution overhere and i will see it when im back? sorry for that
chance*
sturdy ruin
we'll write the solution here
fluid frigateBOT
fleet coral
👋 Taking over here, catching up now
The current cycle started at 2025-09-30 22:30:58 UTC, which was the expected date like what you mentioned. Stripe uses UTC for all the timestamp in our system.
The date in your screenshot is likely converted to the local timezone of your system. For example, if you're viewing from a country that is ahead of the UTC time, it'll be seen as the next day as 2025-09-30 22:30:58 UTC + 2 hours (viewed as local time) can be the next day
fluid frigateBOT
summer jasper
reduce_subscription-period
Did you look at the SubscriptionSchedule, how it was created, what its phase(s) looked like, etc.?
summer jasper
Sure but it had one right? And you were asking what happened. Ultimately you have a Subscription anchored on Aug 30, and then it renews on Sep 30, that's a month
hollow sage
hmm im not sure. where Can i check it?
if it had one?
because field in api response is null so it must be unattached
summer jasper
Did what I explain solve you problem? Like the part about 30?
hollow sage
If it was 100% subscription schedule it does. but I cant see any data that tells me there were subscription schedule
summer jasper
Okay I'm lost now 😓
Can you reframe your question clearly? What is bothering you about that Subscription exactly all in one sentence?
hollow sage
Okay one more time 😄
hollow sage
First my question was why subscription started of 31 and next billing period is not from 30 but from 1 and You explained me that that is timezone issue right?
Yeah
summer jasper
That Subscription is from August 30 to September 30 in UTC which is one full month
But if you are ahead of UTC like in Japan, you see August 31 to Octber 1 because September is 30 days so you see the next day.
summer jasper
I mean that's it, there's nothing else to this
hollow sage
welll
it had to be my misstake im sure that i seen from 1 to 30 and that confused me but I cant see this now 🤔
o here
check this please
oh OMG
im stupid
and blind
thank You for the response
and Your time
summer jasper
Sorry for the long back and forth
I literally have a KB article internally I wrote many years ago about exactly that issue because it's so subtle to grasp
summer jasper
sure, you too 🙂