#nickdnk_error
polar cradleBOT
👋 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/1341573321413627965
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- nickdnk_api, 4 days ago, 16 messages
rugged mesa
Hey Nick! Looking...
graceful plinth
This chain of events in particular is kind of odd
Look at the dates, it's a customer object deleted a while before this happened
I only encountered this because I somehow had deleted our test customer object for an account and then tried to attach a payment method, which worked, and then I got a "customer does not exist" when i tried to retrieve it
Followed up with this to retrieve the customer and payment method, which of course failed: req_h21WFsdrAke22p
evt_1QtdOWL7ilRdQXxElg6CCGko is the event
and evt_1QtdOWL7ilRdQXxEU6V42HxW
rugged mesa
This Customer was part of a Test Clock. The times you're seeing are test clock times, not actual times. The request to create the Setup Intent happened on 2024-12-16 22:09:21 UTC realtime and 2025-01-15 23:00:00 UTC Test Clock time, but the Customer in question wasn't actually deleted until 2025-02-09 17:43:43 UTC.
The Setup Intent was confirmed after that, on 2025-02-17 23:06:31 UTC, but it wasn't created before the Customer was deleted as far as I can see.
graceful plinth
I created the setup intent yesterday, the customer object was deleted on februar 9
rugged mesa
Also note that it looks like the Customer in question was automatically deleted when the Test Clock was deleted.
graceful plinth
Or I may have created it before, true, but should it not fail a confirmation?
yea maybe this is just test clocking tripping me up
But does test clock delete the customer entirely?
rugged mesa
It was created back in December: https://dashboard.stripe.com/test/logs/req_SrM9fbSvAb9dXr
graceful plinth
It was created back in December: https://dashboard.stripe.com/test/logs/req_SrM9...
Correct, but shouldn't it fail to attach the payment method if the customer does not exist?
evt_1QtdOWL7ilRdQXxEU6V42HxW this one I mean
polar cradleBOT
rugged mesa
Yeah, that part is a bit strange and is likely a bug. The rest seems ~normal to me (or as normal as time travel in test mode can be). I'll flag that internally.
graceful plinth
I would agree, but I also recognize that creating a setup intent, deleting the customer, then confirming the intent is a very odd thing to do
Does test clock delete my customer? Because I don't remember doing that myself
(We dont have any code that does this ever)
Yea looks like it was deleted automatically; evt_1QqeXkL7ilRdQXxE9QdQbzfr
Did not know
rugged mesa
Everything inside a Test Clock is deleted when the Test Clock is deleted, yeah.
rugged mesa
See here for details about Test Clock deletions, including the fact that we automatically delete Test Clocks after 30 days: https://docs.stripe.com/billing/testing/test-clocks/api-advanced-usage#delete-clock
graceful plinth
If there is one thing we learned from Back to The Future, it is that you don't mess with the fabric of time, so I can excuse this
graceful plinth
No problem
rugged mesa
Beyond that, though, I think this is mostly a case of Test Clocks being a bit hard to grok in some scenarios. 🙂
graceful plinth
Yeah, I just got really confused because I didn't recall deleting the customer and I also didn't understand how I could successfully attach, then get told the customer doesn't exist, so for a second I thought we had some crazy bug
rugged mesa
Yeah, makes sense. There is a bug in there, it's just not a huge one thankfully.
polar cradleBOT