nacho_timestamp-milliseconds | Stripe Developers | Page 1

floral barnBOT May 28, 2024, 4:28 PM

#

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

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

mighty kettle May 28, 2024, 4:30 PM

#

nacho_timestamp-milliseconds

#

@left hull you need to make sure that your timestamp is not more than 5 years in the future.

left hull May 28, 2024, 4:31 PM

#

I saw the error message

#

but I have been creating subscriptions that ends in 20 years in the future

mighty kettle May 28, 2024, 4:32 PM

#

Gotcha, we recently made a change that validates the timestamp properly. We had a bug where we allowed milliseconds instead of seconds and we fixed it last week I think.

left hull May 28, 2024, 4:32 PM

#

did that changed? when? is there any publication explaining it?

mighty kettle May 28, 2024, 4:32 PM

#

I'd recommend reaching out to our support team about this: https://support.stripe.com/contact

left hull May 28, 2024, 4:32 PM

#

no, it's not that

#

before there was a check that the subscription does not end in more than 20years in the future

#

so I had to make sure that didn't happen

#

but now I see it was made much more lower than that and we were not notified in any way

mighty kettle May 28, 2024, 4:34 PM

#

Yes I think it's because of what I said. We added validation for unix timestamps and I think it caused this issue. That's why the best next step is to reach out to our support team: https://support.stripe.com/contact

left hull May 28, 2024, 4:35 PM

#

ok, thanks, I'll make sure our product team reaches out to them but can you help me finding a workaround?

#

e.g. create the subscription without the cancel_at timestamp would make it work?

mighty kettle May 28, 2024, 4:36 PM

#

yes

left hull May 28, 2024, 4:50 PM

#

I consider that I could have been helped better in this situation, the opposite experience as I always had when asking for help in this channel; the problem is still not solved and the answer were short and helpless

#nacho_timestamp-milliseconds