You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently, I noticed that when a subscription expires, it is typically described as follows from LS doc:
"The subscription has ended (either it had previously been cancelled and the grace period created from its final payment has run out, or it was previously unpaid and the subscription was not re-activated during dunning). The ends_at value shows the date-time when the subscription expired. Customers should no longer have access to your product."
However, I observed that when a user attempts to upgrade their plan and the payment fails, the subscription status immediately changes to "past_due" . It is acceptable till that But after the user cancels the plan, it changes to "expired" without a grace period. This behavior seems inconsistent with the expectation that a grace period would apply before the subscription is marked as expired.
The text was updated successfully, but these errors were encountered:
Recently, I noticed that when a subscription expires, it is typically described as follows from LS doc:
"The subscription has ended (either it had previously been cancelled and the grace period created from its final payment has run out, or it was previously unpaid and the subscription was not re-activated during dunning). The ends_at value shows the date-time when the subscription expired. Customers should no longer have access to your product."
However, I observed that when a user attempts to upgrade their plan and the payment fails, the subscription status immediately changes to "past_due" . It is acceptable till that But after the user cancels the plan, it changes to "expired" without a grace period. This behavior seems inconsistent with the expectation that a grace period would apply before the subscription is marked as expired.
The text was updated successfully, but these errors were encountered: