#gabor-hiya_webhooks
midnight jungleBOT
👋 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/1326588179289214989
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
half acorn
Invoice item shows Dec 17-16
icy egretBOT
vagrant flame
Hi there 👋 taking a look at that Invoice that you shared.
half acorn
Thanks
vagrant flame
I'm trying to make sure I understand what led to this Invoice being generated correctly.
This Invoice was created when you canceled the associated Subscription, is that right?
half acorn
Yes
vagrant flame
Do you have other examples of Invoices where this happened? And if so, what is the most recent example that you have?
(That shapes how I will look into this on our end a bit)
half acorn
This was the most recent one
I will look up more, give me a min
Here is another invoice for a different customer:
https://dashboard.stripe.com/test/invoices/in_1QVWJEGhDr1u9rxFBv6q5Zjm
Another for another customer:
https://dashboard.stripe.com/test/invoices/in_1QVEvaGhDr1u9rxFpdRoj6Rz
midnight jungleBOT
half acorn
For the record this phenomenon only has happened in test environment.
vagrant flame
Oh, thank you for that context! I don't want to discount the importance of it just because it's only in testmode, but it does give me an additional idea of something to check on.
Hm, it doesn't look like you were using Test Clocks here to help with testing. Is that correct?
https://docs.stripe.com/billing/testing/test-clocks
half acorn
We have used test clocks for some customers, but not for these.
For some reason customers have been automatically deleted where we had used test clocks.
vagrant flame
That's expected behavior when the Test Clock is deleted (the simulation is flagged as finished). Since those objects are running against a different time than the rest of the account, they are removed because they can't be resynced back to the current time.
half acorn
Okay, that is a non-issue for us.
vagrant flame
Is this something you're able to consistently reproduce? (the issue with the intervals being backwards or having the wrong ending time)
I'm not seeing any mention of this on our end and believes this needs to be reported to the appropriate product team for further investigation. To go with that report I'm trying to confirm if there are steps that can be consistently used to reproduce this behavior.
half acorn
I have a total of 16 occurance of this happening in test mode.
As far as I see they are all related to subscription cancellation.
Just reproduced via cancelling a subscription (invoice is still draft):
https://dashboard.stripe.com/test/invoices/in_1Qf2kIGhDr1u9rxFzgVYGzD8
merry birch
Hello! I'm taking over and catching up...
half acorn
So what I usually see:
- period.start: the correct epoch timestamp
- period.end: the start of the day the cancel was done (08/01/2025 00:00:00 UTC in case of the last one)
But on the invoice it displays the previos day for period.end
merry birch
I was looking at this along with Toby and it does seem like a bug on our end. We'll flag it internally for further investigation and a fix.