#pavlina_api
vestal kayakBOT
👋 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/1460987143496142908
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
wintry current
👋 Hi there, just taking a look now
Can you share any of the related request IDs (req_xxx)? https://support.stripe.com/questions/finding-the-id-for-an-api-request
wintry current
Yes, thanks, I can find the subscription from there. Taking a look
eternal beacon
Thanks
wintry current
Can you clarify what you mean by the next attempt value being wrong? Are you referring to the event you specified above (evt_1SpTqmAZplvGSnJjHqyiqz4E)
eternal beacon
Yes. I have my settings set as up to 4 retries in 3 weeks with Smart Retries. The above event is the 4th retry but it has a next_payment_attempt value so it will be a 5th retry which I find incorrect.
THis event in particular seems like it shouldn't have triggered evt_1SpTrjAZplvGSnJjqiQgICr1
"attempt_count": 5
wintry current
I believe that count includes the original attempt, so it's counting the original attempt + 4 retries
So the event above is the 4th attempt, but 3rd retry
eternal beacon
Can I somehow distinguish those?
wintry current
Any attempt >1 should be a retry
eternal beacon
So the initial fail is attempt 1 and anything after comes from my settings?
But then on the final attempt first I got the customer.subscription.deleted then the invoice.payment_failed event
vestal kayakBOT
eternal beacon
Hello
modest mortar
Hi there, can you clarify the remaining open question? The initial payment attempt/failure is not a retry, so yes you would get 5 total payment failures if you configured 4 retries.
eternal beacon
Yes, that was my initial confusion, because the initial retry is marked as attempt 1 so I thought this was 1st from the 4th retries set up. So the attempt 1 will always be there no matter if I have 0 attempts set up in my dashboard?
modest mortar
Yes, there will always be the initial payment attempt for the renewal invoice at finalization, even if you have no retries
eternal beacon
Okay, thank you!