#yuliahydrow_test-clock-invoices-and-paid-at-issue
1 messages · Page 1 of 1 (latest)
👋 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/1431042062676918295
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there
Hello
looking
Hi there,
takingover for my colleague. Let me quickly catch up...
Hi, let me know if you need more info
For event evt_1SJ4r2E1ba98qjoYOS6NrLyj I look at the Invoice Pay request that came from your integration, and it has the timestamp 8/24
for event evt_1SLUIpE1ba98qjoYAbxs0lnM the pay request was made on 8/30.
This seems like an issue with the time clock.
Correct, for the 8/30 event, I was expecting the paid_at timestamp is 8/30 but it's set to 10/23 (today)
The first event was correct and it has been correct for the past 2 years because this is in our automated tests that we haven't changed
This test just started failing in the past 2-3 days.
We are also seeing other random behavior with test clock lately but let's focus on this issue for now.
Still looking, but I might need to move this thread to email because it will require a deeper investigation than what we offer here on discord.
But still looking into this
When I look at the Invoice in_1SLUIWE1ba98qjoYmyENRunI, I can see the creation request https://dashboard.stripe.com/acct_1EXE5YE1ba98qjoY/test/logs/req_QvWMWrWvDrk9k0
According to the time clock it was created on **2024**-10-23
Yes, it was created before the test clock was advanced but like I said the other invoice was also created the same way but with different results. Let me know if you have to create a support ticket so I can follow up.
Ok, it seems like this is a known issue when using test clocks and invoicing. I do not have a solution to offer rightaway but what we can do is moving this conversation to email and connect with the product team for further investigation. Is that ok with you?
Yes
Ok, you will receive a DM in a second with instructions to create a support ticket that goes directly to our team
Hello @cosmic bough, we have sent you a direct message, please check it at https://discord.com/channels/@me/1431055540028444843
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
did you create a ticket? I don't see anything on my end yet.
I will close this thread now. You will still be able to create the ticket through the DM you should have received. You can also open a new thread if needed. In that new thread we will see a reference to this thread.