Understand QCMM Renewal Successors and Membership Transition Order

QCMM uses a hard lifecycle order for linked renewals: finish the predecessor’s expiration transition first, then activate the due successor. This makes access changes deterministic and repairable.

The Successor Keeps a Predecessor Link

A renewal successor stores the predecessor membership relationship. If its start time is in the future, the successor is Scheduled rather than Active.

Expiration Must Be Durable Before Activation

When a scheduled renewal becomes due, QCMM first verifies the predecessor. The predecessor must have reached its end date, its stored status must be Expired, Joomla-group reconciliation must succeed, and an expiration-processed marker must be written and read back successfully.

Only Then Are Successor Groups Added

After the predecessor transition is proven complete, QCMM assigns the successor’s active Joomla groups, changes the successor to Active, and reconciles the user’s remaining required groups. If expiration or group work fails, the successor stays Scheduled so the task can retry safely.

Two Tasks Support the Lifecycle

Membership Transitions runs every 5 minutes for prompt due expirations and scheduled-renewal activation. Lifecycle Automation runs every 60 minutes for broader lifecycle checks, reminder email, duplicate prevention, and related cleanup.

Why This Design Matters

The ordering prevents a successor from becoming active merely because an update was attempted. It also prevents predecessor cleanup from removing access that the successor still requires.

Community Discussion

Want to compare membership workflows or share practical QCMM tips? Visit the QC Memberships & Meetings Community. For private support, account-specific billing or entitlement issues, or feature requests, use the QuantaCade support system.