#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/1486003294210883684
๐ 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.
- katscap_api, 15 hours ago, 34 messages
Hey there, taking a look at this
just a few things:
1/ It does not look like you actually changed the default_payment_method on the sub you shared, i still see teh 0341 card on that sub
2/ Can you try advancing the test clock again (eg, another hour or day) after being past the next attempt time? It is possible this needs to move forward again to trigger the retry. Some async effects require "two steps" of the clock to happen.
whoops, sorry let me add the new payment method and advance the test clock again.
3/ I see you're attaching a test clock to an existing customer via the Dashboard. Can you try instead creating the test clock first and then create the customer with that test clock (as shown here) to see if the results are different?
yes, will try that
new sub: sub_1TEW7xGTP9rLKLKtl8PTzTRv
going to change the payment method, then advance the clock
ah, it did work this time!
thanks everyone who helped me on this!
Hi again! So happy to see this working after our investigation yesterday ๐ We're going to investigate why this isn't behaving as expected with test clocks via the Dashboard but please create them via the API for now to unblock your testing.