#kt_test-clock-payment-attempts
rare basinBOT
👋 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/1336383476399607979
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
zealous cobalt
sly badge
Hi hi! Can you share the Subscription ID with me please?
zealous cobalt
sub_1Qop3gBCxN7wn3Lgvj1puolg
zealous cobalt
also this one I just tested on a different account sub_1Qoq4FAFQUUIWEfk4U7N2qCf not sure if that's helpful 🤷♀️
sly badge
Awesome. Just taking a peek.
sly badge
The Customers in both of those Subscriptions don't have a Payment Method, so there's nothing to use to retry - and past_due invoices won't get retried automatically.
Also the 0341 test card that you used will never work past the 'attach to Customer' step.
https://docs.stripe.com/billing/subscriptions/overview#unpaid-subscriptions
zealous cobalt
I've tested with this scenario in the past though and it worked? The invoice status is open and the customer does have a payment method attached to them for both test subscriptions I sent you, it's the 0341 card that I would expect to still be run but fail. In the past when I've run this exact scenario I've seen it retry the invoice and fail
sly badge
Can you share an ID related to when this was successful in the past?
zealous cobalt
I don't have one, we haven't tested our failed payment handling in a few months and the subscriptions + test clocks are deleted after 30 days
but if the invoice status is open and there is a card on the customer then shouldn't the test clock retry on the day that it says "Payment will be retried X/XX/XX"
topaz spindle
fyi i'm managing the thread now as my colleague has to run. there are a lot of open threads so my responses might be a little slow.
zealous cobalt
okie dokie, no problem
topaz spindle
ok circling back to this now
just double checking i understand the question, the only unexpected behavior here is that the payment is not being retried automatically?
zealous cobalt
yep!
the decline code is "generic_decline" so it doesn't fall into non-retryable decline codes
topaz spindle
ok cool, i'm going to need to see if i can reproduce this real quick
topaz spindle
just acknowledging that i'm still working on reproducing the issue
zealous cobalt
oooh interesting, if you look at this sub sub_1QoriPBCxN7wn3Lg6B6p8RmR the first invoice in the subscription didn't retry in the simulation but the renewal invoice for the next month of the subscription did in_1QornHBCxN7wn3Lgq2vVTto9
that's probably good enough for me to run the test I need to run but still odd that the first invoice didn't retry, seems like something funky with the test clock feature
topaz spindle
yeah i'm seeing the same thing in my test....
i was searching the docs to see if there was anything specific to smart retries behaving weirdly with test clocks but i don't think we have that documented