Universal Containers is using Communications Cloud Order Management and just onboarded their enterprise sellers and regional champions from various regions. After adding these sellers, the volume of orders has gone up considerably and orchestration is failing because the number of Apex jobs queued is exceeding the maximum allowed.
What should a Consultant suggest to mitigate the orchestration errors?
In Salesforce Communications Cloud Order Management, orchestration steps execute through Apex-based orchestration jobs. When order volume rises sharply---as happens when additional sellers or regional teams begin submitting orders---the system may hit Salesforce's platform limit for queued Apex jobs (50 number of licensed Salesforce users). Once this limit is reached, orchestration fails.
Salesforce's official scalability recommendation is to enable Platform Events for Orchestration. This switches Order Management from synchronous Apex-queue processing to asynchronous, event-driven orchestration, which drastically reduces reliance on Apex jobs. Platform Events allow OM to process far more concurrent orchestration steps without hitting queue limits and provide better throughput and resilience for enterprise-scale flows.
Options A and B are incorrect because Salesforce does not increase Apex job limits, and splitting orders is not a best-practice. Option D reduces automation and violates OM design principles.
Currently there are no comments in this discussion, be the first to comment!