#waldeedle_unexpected

1 messages · Page 1 of 1 (latest)

pallid hollowBOT
#

👋 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/1370070216507129988

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

edgy fulcrum
#

Hi! Thanks for sharing the ID! Let me take a peek. 🙂

#

Hi! So ... the 29th is the last day of February, so that sort of makes sense, but I also understand how that would be unclear. I feel like I've run into this before - let me see if I can find some documentation around it.

warm radish
#

A monthly subscription with a billing cycle anchor date of January 31 bills the last day of the month closest to the anchor date, so February 28 (or February 29 in a leap year), then March 31, April 30, and so on.

#

right but my date is Feb 29

#

so shouldn't it have been 29 for the other months

#

"billing_cycle_anchor": 1709251200,

#

oh I see

#

Fri Mar 01 2024 00:00:00 GMT

#

the utc timestamp is at midnight of march 1

#

sorry I was confused, that makes a lot of sense now

edgy fulcrum
#

And that's still the 29th where you are, ya?

warm radish
#

ya my account is set to be on Regina time and my golang code also looks for CST so thats where the difference is coming from

#

I already addressed the bug in my code previously, this is just a relic from before I guess

#

thanks again!