Scheduled subscription cancellation downgrades namespace directly
Problem
When there is a scheduled cancellation for a subscription, the related callout downgrades the namespace directly without checking the date of the cancellation. For example, this subscription was scheduled on March 23rd to be cancelled on April 1st, it resulted in downgrading the linked namespace directly with the creation of the cancellation (log).
Additionally for the general processing of a cancelled subscription's callout, when a subscription isn't linked to a namespace, the callout doesn't process the inactive subscription at all due to an early exit here.
Proposal
When processing a callout for a scheduled cancelled subscription (code), the used service (ProcessInactiveSubscriptionService
) should schedule a sidekiq job to take care of processing the inactive subscription instead of processing it right away.
Additionally, callouts for cancelled subscriptions that have no linked namespace should still update the CustomersDot's Order
.
Result
- Downgrade namespace on the day of the actual cancellation if it's future dated and not directly when the callout happens.
- Update the CustomersDot's
Order
for the cancelled subscription to reflect the correct state.
Support Priority Score: (1, 3, 3, 2, -, 3, 3, 2, 3, -, 3) => 23