reactivate a recurring subscription

Hi,
could you please clarify what reactivate means and when the option occurs ?

Recently a member had the option to reactivate, but we don't understand why, as the payment went through as usual.

The plan is
Regular Validity duration - 1 month
'Total number of occurrences of regular validity/price' - 0.
Auto-recurring renewals - Yes
Grace period before real expiration - 1 day (maybe this needs to be higher ?)

The Stripe subscription debited the card successfully on the correct day it was due (the 30th of the month), so I would have expected her membership to be active. This was the 4th month of the subscription. All previous months, the payment was on the 30th and there were no previous problems with the Joomla membership.
But this time, on the subscription tab of her profile, it said that the membership 'Expired 30/10/20 '

Thanks

Grace period before real expiration - 1 day (maybe this needs to be higher ?)

If you're using recurring payments this should be typically set to at least 3 days. This is to ensure any delays on the payment processors end won't cause a subscription to prematurely expire.

But this time, on the subscription tab of her profile, it said that the membership 'Expired 30/10/20 '

This typically only happens if an IPN doesn't reach your site. Check within CBSubs > Notifications to see if you got an IPN for that payment. Also within your Stripe Dashboard under Developers > Webhooks click your webhook URL and review the "Webhook attempts" and "Log" at the bottom to be sure the Webhook didn't report as failed.

Be sure CBSubs is completely up to date and within Stripe > Dashboard > Developers you've the latest API activated under "API version".

An IPN with 'subscr_payment' and 'Completed' was received on Oct. 30.

On the Stripe Dashboard, under Developers > Webhooks, when I click on the webhook URL and review the "Webhook attempts" and "Log" and then click on 'Failed' to display just the failures, there are 'No matching results'

Also, when I search the cbsubs history logs for her email address, there is a message on October 30th 'Updating payment record because of new status of payment basket: Completed because of event received: subscr_payment. Previous status was: Completed'. This is the same message seen on September 30th and August 30th.

CBSubs was completely up to date.
Stripe did not have the latest API activated, but it does now. Could this have caused it ? What's strange is that other payments have come through since then without a problem.

We have resolved the situation by cancelling the subscription in Stripe and asking the user to 'reactivate' the subscription and enter their card details again. So this is not really a problem for us at the moment. I'm just trying to understand why it happened in case I need to do something to prevent it happening again. But if there is nothing obviously wrong then I don't mind just leaving it. I just don't understand why it happened.

Thanks

Please PM backend super user login credentials and include the username of the user that had this issue. Will review the notification and logs to see if a IPN state maybe not being handled properly. It should've reactivated based off the information you've provided so far.

Stripe did not have the latest API activated, but it does now. Could this have caused it ? What's strange is that other payments have come through since then without a problem.

Possibly, but shouldn't since we've IPN version backwards compatibility implemented for quite a few versions back.

Have reviewed your install and I can't make any sense of why it expired. The IPN is there, the payment row is there, the history log of the basket being updated just like previous renewals is also there. There are no hints or notes of any kind of error. Everything looks as it should. Very strange the subscription expired somehow.

Reviewing the log of the subscription itself shows it did expire, but that it also renewed. Specifically it renewed fine on "30/10/20 17:42:40 PM" then for some reason expired on "31/10/20 16:43:55 PM". I've checked a couple of your other auto recurring subscriptions and they appear to be logging fine and renewing fine so I'm not sure why this users subscription specifically is behaving so strangely. It is possible this was a bug that has been fixed since that user initially subscribed.

What I do recommend is being more generous with "Renewable in advance by" and "Grace period before real expiration" within your auto recurring plans. Both should be set to at least 3 days. This allows for IPNs to arrive early or late without causing the subscription to prematurely expire or fail to renew. It's entirely possible there was just a timing problem happening.