#katscap_api
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/1485708176728002631
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello! Sorry for the delay, we've been juggling a few threads. Taking a look now ๐
no worries!
Do you have a request ID or the subscription ID for me to investigate?
yes! this is the subscription ID: sub_1TECuKGTP9rLKLKt9twwzPeO
Alright, I see requests for:
- Creating the subscription with a payment method for the 0341 card https://dashboard.stripe.com/acct_1SdITLGTP9rLKLKt/test/logs/req_e22sQGMu3jaHgT
- The initial payment attempt failing https://dashboard.stripe.com/acct_1SdITLGTP9rLKLKt/test/logs/req_iIcAMEhEcENVbH
- Updating the subscription with a payment method for the 4242 card https://dashboard.stripe.com/acct_1SdITLGTP9rLKLKt/test/logs/req_K1Ql3QlXt7qtJl
I also see the next retry is March 24 so everything looks as you described ๐
How are you using the test clock? Are you attaching it to the customer? And do you have a request where you are advancing it?
I actually just go to the subscription in the dashboard and manually advance the time there. This is the test clock id: clock_1TECvPGTP9rLKLKtpme1apjb
Gotcha! I'm less familiar with dashboard functionality but the test clock appears to be attached to the right customer and advanced properly... I'll keep digging, thanks for your patience ๐
Ah got it, thank you.
As far as I can tell, this should have worked! Are you able to try this flow again with a new subscription to see if it fails every time or was just a one-off?
I tried it twice with two different subscriptions with the same result, but let me try it again. I'll keep you updated!
Thanks so much! I'll try and reproduce it as well. If it's consistently failing, we might have a bug on our hands.
just created this new subscription with the failure card: sub_1TEERGGTP9rLKLKtmGoPSD2O
says it will retry on march 24
updated the payment method on the subscription to ****4242
advancing the test clock to march 25...
same result!
Looks like the test clock is frozen at 2026-03-25 19:49:00 but the invoice retry date is 2026-03-24 19:51:03 so it needs to be advanced further, right?
Oh sorry! I was looking at the time and not date.
no worries!
Okay, trying to reproduce on my own account now...
thanks so much
were you able to reproduce the issue?
My apologies, I had some trouble reproducing but should have an update soon. Thanks again for waiting ๐
no worries, thanks again
Alright - I tried a few different flows but wasn't able to reproduce. Advancing the test clock succesfully retries the payment for me.
I'm curious if creating and advancing the test clock via the API instead of the dashboard might give you a different outcome ๐ค https://docs.stripe.com/billing/testing/test-clocks/api-advanced-usage?dashboard-or-api=api
I know you've been waiting on me for a while so no pressure to try this now but I think it's the best next step. If it still doesn't work and this thread is closed, feel free to start a new thread and link this one for context: https://discord.com/channels/841573134531821608/1485708176728002631