#jairo094215_invoice-retry-logic
primal tangleBOT
👋 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/1349400982932684832
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
near crater
Hello!
We've detected a different behavior in the automatic cancellation of subscriptions due to non-payment.
Previously, if the recurring payment for a subscription failed on a specific date (for example, February 10th), the payment would be retried until the subscription was finally canceled a month later (March 10th). In that case, the next invoice for that subscription, corresponding to the month of March, wasn't generated, since the subscription had been canceled. The problem we're seeing now is that in this same scenario, the invoice for the month in which the subscription expires (March) due to non-payment is generated, just minutes before the subscription is canceled. This problem can be seen in this subscription: sub_1LrOgyDyCiiQ0txVzbpmV170
You can see how the invoice in_1R192qDyCiiQ0txVJCbvm6s8, corresponding to the month of March, was created on March 10 at 18:19, and one minute later, at 18:20, you can see how the subscription was canceled.
umbral cosmos
Hm yeah let me check with a colleague on this
near crater
Great! Thanks
Here you can see an older case where this incorrect behavior didn't occur: sub_1ONLDMDyCiiQ0txVyzV7C7KM
Our "Failed payment handling" policy is 8 retries per month. Could the fact that February has 28 days have had something to do with it?
primal tangleBOT
umbral cosmos
Ok my colleague got back to me. Since you are using smart retries to retry up to 8 times in 1 month, we optimize when exactly these 8 retries will occur. Those retries aren't evenly spaced out and don't occur at the same time each month. So, in the case of sub_1LrOgyDyCiiQ0txVzbpmV170, you just got unlucky that one of those retries occurred right at the end of the billing cycle there and the timing was such that the next month's invoice was generated prior to cancelation
So basically in the current state of things, this is expected
However, I will provide feedback to the owning team that the shouldn't allow this to happen
near crater
Ok, I understand. Anyway, I find it strange since this isn't the only case where this has happened. We've seen numerous cases with the same problem in recent days. Anyway, to avoid this, do you recommend we modify the Smart Retries policy so that subscriptions expire at a different time than a month? For example, 8 times in 3 weeks or something similar
tawdry nimbus
Hi 👋
As my colleague said, this is expected so if your settings are configured the way you describe this is a situation you can wind up in. If you want to retry the invoice payment 8 times, I would recommend reducing the span of time such that you don't overlap the biling period.