krs_unexpected

[tribal bronze]

👋 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/1227130333674213396

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[shell violet]

Hi there, your current billing settings retry card payments for subscriptions up to 4 times within a week https://dashboard.stripe.com/settings/billing/automatic

in_1P0gjeI5vSu94Gk8O7vyk4t9 has already been retried for 4 times, and therefore its next_payment_attempt becomes null because there're no more retries

[spring nexus]

Check this events, i have linked them above, all these events are sent at the same time for invoice update

check the changed attributes, next_payment_attempt is made null and then in the following event to a valid value

and this is recent change in stripe, earlier we used to receive only one event, which will update attmpt count and next_payment_attempt together

[uncut ether]

Do you have an example invoice ID (in_xxx) that only one invoice.updated event was sent when invoice payment was retried and failed?

[spring nexus]

I don't have it handy, but when we implemented the feature it is how it was sent, i am not sure if i can check for the older events now..

found one

https://connect.stripe.com/events/evt_1ON3m8I5vSu94Gk8B43T4IiP
https://connect.stripe.com/events/evt_1ON3n1I5vSu94Gk8JAhvWwt8

[uncut ether]

Thanks for sharing

There might be some changes internally on how the invoice retry attempt is updated and separate events are sent

Can I suggest you writing to Support https://support.stripe.com/contact with example invoices that only had one invoice.updated event with compared to the invoice that has multiple invoice.updated events? So that they can check with the relevant team

[spring nexus]

There is no problem when old value is changed to new value, but when it is changed like old value to null to new value, then it is not correct behavior.

ok.