Loading

Industries Order Management: Orchestration Plan fails with "Invalid conversion from runtime type List to Map" or "Invalid partition"

Publish Date: May 26, 2026
Description
Orchestration Plans in Industries Order Management fail after decomposition in Salesforce Media Cloud and Communications Cloud. This issue typically persists even after configuring all Extract Data Mappers to Ignore Cache.
Symptoms
  • Orchestration plans fail globally or fail to appear in sandboxes after decomposition ("problemas com a decomposição do produto - o plano que foi desenhado não aparece").
    • Error 1: Invalid conversion from runtime type List to Map (A structure mismatch where a list is returned but the downstream consumer expects a single map/object).
    • Error 2: Invalid partition (The Vlocity managed Platform Cache partition CPQPartition is missing, unallocated, or maxed out).
Environment
  • Package: Vlocity CMT
  • Release: Salesforce Summer '24 and later.
  • Profiles: Affects all profiles executing the orchestration runtime, including Integration Users.
Root Cause
Enabling Ignore Cache on a Data Mapper Extractor only forces a bypass of the Data Mapper's individual response cache. It does not bypass the underlying Vlocity managed Platform Cache partition or the "Cached API Response" sObject where the stale or structurally invalid payloads actually reside.
Resolution
Follow these troubleshooting steps in sequence. Steps 1–2 resolve the "Invalid partition" failure; Steps 3–6 resolve the "List to Map" type mismatch.
 
Part 1: Resolve the "Invalid partition" Cache Error
  1. Navigate to Setup > Quick Find > Platform Cache.
  2. Locate vlocity_cmt.CPQPartition. (Note: If missing, the Vlocity Managed Package installation failed to provision it; a package repair or reinstallation may be required).
  3. Click Edit next to CPQPartition and configure the allocations:
    • Session Cache Allocation: Set Trial to 5 MB.
    • Org Cache Allocation: Set Trial to 5 MB.
    • Click Save.
  4. Use the App Launcher to open Vlocity CMT Administration > CPQ Configuration Setup. Search for CacheEnabled and verify its Setup Value is set to True.
  5. In Vlocity CMT Administration, navigate to Maintenance Jobs and execute the following jobs strictly in this order:
    1. Product Hierarchy Maintenance
    2. Clear Managed Platform Cache
    3. REFRESH PLATFORM CACHE (FULL)
  6. Navigate to Setup > Object Manager > Cached API Response (vlocity_cmt__CachedAPIResponse__c). If your data storage limits are maxed out, purge stale records.
Part 2: Resolve the "Invalid conversion from runtime type List to Map" Error
  1. Navigate to App Launcher > Integration Procedures and open the specific Integration Procedure invoked by the failing Orchestration Item Definition (vlocity_cmt__OrchestrationItemDefinition__c).
  2. Open each Data Mapper Action step and review the Output tab:
    • Verify the Output Type strictly aligns with the downstream consumer.
    • Change the type to Map (single record) if the downstream step or orchestration handler evaluates a single object. Use List only if the consumer intends to loop over a collection.
  3. Within the Integration Procedure properties for each Data Mapper action, ensure Ignore Cache is checked (True).
  4. Activate the updated versions of your Integration Procedures.
  5. Flush the runtime changes by re-running Vlocity CMT Administration > Maintenance Jobs > Clear Managed Platform Cache followed by REFRESH PLATFORM CACHE (FULL).
  6. Locate the stuck Orchestration Plan (vlocity_cmt__OrchestrationPlan__c) and click Retry on the blocked Orchestration Item, or submit a new test order through the decomposition pipeline to confirm the plan transitions to an In Progress state without errors.
Knowledge Article Number

005385226

 
Loading
Salesforce Help | Article