Symptoms

A customer purchases a 1 Year(s) subscription. A year later the subscription was about to expire when it was renewed, according to the subscription's autorenewal configuration, for 1 Month(s). As expected, in Commerce, the subscription period changed to 1 Month.

The issue is that when the subscription was renewed in MSFT it was renewed for 1 Year(s) not for a month, leading to a misalignment with CBC.

In the oss logs it can be seen that oss received openapi call to renew subscription:

2023-11-12T02:01:17.106869649Z 12-11-2023;03:01:17,106 INFO  [openapi:159138 openapi:159138 remoting-task-2168 oss] c.p.p.s.x.c.OpenApiMethodReference handling method: renewSubscription invocation of service: core-ear/provisioning-ejb/SubscriptionManagerOpenAPI!com.parallels.pa.service.provisioning.ejb.SubscriptionManagerOpenAPI params: {current_period=1, subscription_id=<subscription_id>, txn_id=<txn_id>, shutdown_date=0, terminate_date=0, current_period_type=Year(s), new_period_type=Month(s), expiration_date=<expiration_date>, new_period=1, order_id=<order_id>, start_date=<start_date>}
2023-11-12T02:01:17.11934183Z 12-11-2023;03:01:17,119 DEBUG [openapi:159138 openapi:159138 remoting-task-2168 oss] c.p.p.s.p.e.SubscriptionManagerOpenAPI renewSubscription eventJson: {"orderId":<order_id>,"newPeriod":{"period":1,"periodType":"Month(s)"},"currentPeriod":{"period":1,"periodType":"Year(s)"},"startDate":"<start_date>","expirationDate":"<expiration_date>"} 

There is also an event in PLM from oss with parameters={orderId=<order_id>, newPeriod={period=1, periodType=Month(s)}, currentPeriod={period=1, periodType=Year(s)}, startDate=<start_date>, expirationDate=<expiration_date>}}: 

Cause

The issue is caused by an Invalid configuration in PPR. Subscription auto-renew to a different period scenario is not supported for the switch to the same plan. By default, all renewal operations for connect products will be processed instantly by PLM without sending any request to the Connect system.

Resolution

Autorenew switch to a period and a different plan was implemented in the scope of PFR-3132 (change order is created in that case).

To align the subscription between platforms, it will have to be terminated in offline mode and re-imported.