#rovarma - Subscription Anchor
mint gorge
Hi rovarma. Looking into this now
Let me ask a colleague about this. My hunch is that your server's clock was just off
Yeah. After discussing this with a colleague, it's almost certainly time skewing. That's the usual culprit
Can you share the request ID of your subscription creation?
autumn cairn
yep, as I said, I suspected it would be clock skew
so it's easy enough to work around, just wondering if there was any official guidance
the ID of a failed request is req_sesyEpXU3m1nf5 for example
buoyant linden
Hello! I'm taking over for @mint gorge. Usually we recommend you read the current_period_end value on the Subscription and base your timestamp off of that in a case like this: https://stripe.com/docs/api/subscriptions/object#subscription_object-current_period_end
autumn cairn
hey! in this case I'm creating a new subscription, so that doesn't apply 🙂
to be clear, it's not an important issue. I know how to work around it, I was just wondering if there are "official" recommended ways of dealing with clock differences between our servers & stripe. If not, that's fine, we'll just fix it on our end
mint gorge
One more quick note before I step out
I'd recommend setting up regular NTP server synchronization
autumn cairn
yeah, our servers have that set up. I encountered this error while testing on my local machine
buoyant linden
Wait, I think I may not understand your question/use case. You're creating a yearly Subscription and setting the billing cycle anchor to a year from when you create it?