#beastboy_testmode-subscription-retention
jagged barnBOT
👋 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/1234873050487324692
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
lost socketBOT
thorny vine
Hi 👋 can you elaborate on what you mean by "these instructions didn't work"?
jagged barnBOT
beastboy_testmode-subscription-retention
thorny vine
Can you copy/paste the ID just above that button here please? The one that starts with sub_.
foggy quarry
sub_1PBGycDyFtOu3ZuTw1IyUPMt
thorny vine
That Subscription was created in a Test Clock, so it's expected that it can't be exempt from retention as it is covered by the Test Clock retention policy:
https://support.stripe.com/questions/test-mode-subscription-data-retention#:~:text=Subscriptions for a customer with an associated test clock cannot be marked as exempt
foggy quarry
Hmm okay so I have to mark it exempt before I fast forward time in the dashboard
thorny vine
No, you don't mark it exempt
What's the concern you're trying to avoid by marking it exempt?
foggy quarry
I need to test a ton of different flows for payment failure / success for a subscription and its a pain having to recreate a bunch of accounts
its fine i already got it marked exempt
thorny vine
Oohh, I forgot we now let you add an existing Subscription to a Test Clock. Honestly I have no idea what happens if you mark it exempt first and then try to add it to a test clock.
foggy quarry
it seems to working
shit it still deletes 😭
damn so theres no way I can keep this subscription alive?
thorny vine
Are you looking at a new Subscription now? The one you shared before is still active.
foggy quarry
sub_1PBHpkDyFtOu3ZuTYwlSjOqM
sorry yes
It's gonna close on july 31st
I would really like it not to though 😦
oh shit!
its auto extending
thorny vine
Is this the one you marked Exempt? I think I see that the retention policy has been disabled for it.
foggy quarry
yes
okay so as it approaches the date, it extends as well. very cool.
thank god man
i was going nuts
thorny vine
Can you help me understand where you're seeing that the Subscription will still be cleaned up by a retention policy? I'd like to take a closer look at that and see if it's something we can improve upon, to make it more obvious when that policy is disabled.
foggy quarry
Sure
foggy quarry
shit it still deletes 😭
Actually I'm not seeing that it'll be cleaned up. I was assuming that based on this screenshot here, where it's saying I can only advance it to a 'max' date, but I didn't realize that the 'max' date is just the current date + 2 months.
thorny vine
Ah, yeah, that's a Test Clock limitation. You can only advance up to 2 billing periods (exact interval depends on the underlying Subscriptions)
foggy quarry
I think it would be helpful in your docs to mention that if you want to exmpt a subscription from the retention policy and still use test clocks, you must exempt it before you 'attach' the test clock to it (which is done automatically via stripe in the dashboard when you advance time)
Wasn't very clear to me ^
thorny vine
Agreed, that's definitely something I'm going to play with more later. Both the exemption marking flow and the ability to attach an existing Subscription to a Test Clock are dashboard only features. So my team and I aren't the most familiar with them (we primarily focus on helping with our API in this forum. I'll take a closer look and file feedback if there's room for improvement there.