#garybernhardt_unexpected

1 messages ยท Page 1 of 1 (latest)

trail grailBOT
#

๐Ÿ‘‹ 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/1313586901495713792

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

sharp mirageBOT
heady ferry
cedar cipher
#

Right. It's been set to "If all retries for a payment fail, [cancel the subscription]" for years

heady ferry
#

Do you have an example of a Subscription that you can share where you feel your account settings weren't adhered to?

cedar cipher
#

Yes. Can I paste the ID here?

heady ferry
#

Yup

cedar cipher
#

sub_1OHIxvDU21w5evhbXQWBeCrL

heady ferry
#

And which of the Invoices for that Subscription do you think should have triggered the cancellation? Looks like several new ones were created due to recent update requests being made for the Subscription.

cedar cipher
#

I only see three invoices, one per year (Nov 26 2022, Nov 27 2023, Nov 27 2024). The Nov 27 2024 invoice is in_1QPzPRDU21w5evhbn9VfQo1s. The charge for that invoice failed at 12/1/24, 5:34:16 PM. Then ~1.5 hours later at 12/1/24, 7:11:43 PM, the invoice was voided and the subscription was set to cancel at period end, both in the same second, so the cancelation must have been an automatic response. But it was "cancel at period end", not an immediate cancelation

#

Net effect is this user (an several other users I've seen this happen to) gets a free year despite a decline + void

heady ferry
#

Your current subscription setting is to retry payments up to 4 times over two weeks, neither of those thresholds were hit for the Invoice you referenced. So the retry schedule wasn't exhausted and the behavior to cancel the Subscription wasn't invoked.

This request was then made from your backend to set the Subscription to cancel at the end of the billing period:
https://dashboard.stripe.com/logs/req_lZQBF9wz8FfmMr
and this one was made to void the Invoice:
https://dashboard.stripe.com/logs/req_Q9KkMuBY4poZZ4
neither of those were done automatically by our system.

cedar cipher
#

Yep, you're exactly right. I found the bug instantly once you pointed that out. I feel silly, but thank you for the quick and clear help!