Fix: Extension Period MACD Fails with csordcb Null Pointer (Invalid Observer Metadata)

Solution

Error Signature

You may see an exception during Extension Period MACD / new order creation such as:

• System.NullPointerException: Attempt to de-reference a null object (namespace csordcb)

Often reported while calling:

• csordtelcoa.API_V1.addSubscriptionsToMacOpportunity(List<Id> subscriptionIds, Id opportunityId, Boolean processAsync)

When This Occurs

This pattern can occur during CloudSense observer processing, where CloudSense loads observer registrations from custom metadata and attempts to instantiate and dispatch them.

Root Cause (Confirmed)

An entry in the CloudSense Observer custom metadata type csordcb__Observer__mdt contains a value in csordcb__Class_Name__c that references an Apex class not present in the org.

Example observed: CSMassMacdJobStatusHandler was referenced by an observer record, but the Apex class did not exist.

Diagnosis

1. Run the following SOQL query (Developer Console / VS Code + Salesforce extension / Workbench):

   select Id, DeveloperName, csordcb__Class_Name__c
   from csordcb__Observer__mdt
   order by SystemModstamp desc

2. For each returned csordcb__Class_Name__c value, verify the Apex class exists in the org (Setup → Apex Classes, or by querying ApexClass by name).

3. Identify any observer entries where csordcb__Class_Name__c is populated but the corresponding Apex class is missing.

Resolution

Choose the option that best matches your implementation.

Option A (Common): Remove or Correct the Invalid Observer Registration

1. Go to Setup → Custom Metadata Types.
2. Locate the type Observer (API name: csordcb__Observer__mdt) and open Manage Records.
3. Find the observer record whose csordcb__Class_Name__c points to a missing Apex class.
4. Delete that custom metadata record, or update it to reference a valid class (if appropriate for your configuration).
5. Retry the Extension Period MACD action or re-run addSubscriptionsToMacOpportunity(...).

Option B: Restore/Deploy the Missing Apex Class

If the observer is expected to run in your org (for example, it is part of a customization package you maintain), deploy/restore the missing Apex class so it matches the metadata registration, then retry the MACD flow.

Verification

• Re-run the same operation that previously failed (UI-driven Extension Period MACD order creation, or the same anonymous Apex invocation of csordtelcoa.API_V1.addSubscriptionsToMacOpportunity(...)).
• Confirm the process completes without System.NullPointerException: Attempt to de-reference a null object in the csordcb namespace.

Notes / Cautions

• Only remove an observer registration if it is not required for your business flow. If it is required, restoring the missing class is typically the safer approach.
• If behavior differs across orgs (for example, UAT works but a sandbox fails), compare csordcb__Observer__mdt records and the presence of referenced Apex classes across those orgs.