Skip to main content

Hi community, 

 

We're stuck on **Consumer Goods Cloud Processing Services** in a new implementation project sandbox and would appreciate any experience or guidance. 

 

## Environment 

- **Org:** Sandbox, Summer '26 (API 67.0) 

- **Package:** `cgcloud` 262.2 (Enhanced Data Model) 

- **Feature:** Penny Perfect Pricing V2 — `ScheduleCGCloudServiceComplexPricing` 

 

## Issue 

All Processing Services batch jobs fail in the same place when

onBackendV2 runs as a @future

: 

 

Session not found - Session Cache not supported` 

 

Apex logs show 0 `CALLOUT_REQUEST` / `CALLOUT_RESPONSE.  

The failure happens after loading `Off_Platform_Endpoint_Map__mdt` (114 rows) and before any `OffPlatformCallout` HTTP call. 

 

Affected classes (same error pattern): 

- `ScheduleCGCloudServiceComplexPricing` 

- `ScheduleCGCloudServFlattenAccHierarchy` 

- `ScheduleCGCloudServiceFlattenOrgUnit` 

 

AsyncApexJob shows: Completed, Errors = 0 — the exception appears to be caught internally. 

 

## What we've already configured 

- Processing Services Pairing App → Connected / registration complete 

- ECA: CG_Cloud_Processing_Services + JWT cert CGCloud_Services 

- Integration user: CGC Processing Services Register PSL + CGCloud Retail Business Admin 

- PS user: Register PSL + Advanced Pricing / Flattening worker permission sets 

- Platform Cache cgcloud.CGCPSSession: Session = 2 MB, Org = 0 MB 

- System setting CGCloudServiceComplexPricing = true (PPP V2) 

- Batch Process Configuration: Flatten Acc, Flatten Org Unit, Complex Pricing (SO 0001) 

- cgcloud.Scheduler scheduled hourly — fires successfully 

 

## Outcomes 

- CP_Pricing_Condition__c = 0 

- Batch_Run_Status__c = 0 

- Pricing Condition Stage records remain unprocessed (Status = `n`) 

 

## Our understanding 

The managed package appears to resolve off-platform session via Cache.Session / partition cgcloud.CGCPSSession inside @future. Platform Session Cache is not available in async Apex — which matches the error text. 

 

Pairing UI "Connected" and inbound JWT (PS → SF Login History success) don't seem to populate whatever session state `onBackendV2` needs for outbound callouts. 

 

## Questions for the community 

1. Has anyone seen this exact error with Processing Services pairing showing Connected? 

2. Is there a missing bootstrap step after pairing (beyond BPC + Scheduler) that populates off-platform session for async batches? 

3. Any known issue with cgcloud 262.x on Summer '26 sandboxes? 

 

Thanks in advance — we'll also open a Salesforce Support case, but hoping someone in the community has hit this before.

1 resposta
  1. 27 de set., 13:12

    Hi João,

    The fact that there are no CALLOUT_REQUEST / CALLOUT_RESPONSE entries and the exception occurs before OffPlatformCallout strongly suggests the failure is happening while the managed package is trying to obtain the Processing Services session, rather than with the endpoint or JWT callout itself. 

     

    Since the pairing is already showing Connected, I would check whether the Processing Services registration/bootstrap has successfully created the session expected by onBackendV2. In particular, I’d verify the pairing/registration logs and compare the setup with a known working org, including the CGCPSSession cache partition and the Processing Services integration user.

    I’d also test the same operation synchronously, if the managed package provides any supported way to do that. If it works synchronously but fails only from @future, that would further isolate this to the async session handling.

    Given that the same error occurs across Complex Pricing and both Flatten services, this looks more like a common Processing Services/session issue than a problem specific to PPP V2.

    I’d include the following in the Salesforce Support case:

    • cgcloud package version 262.2
    • Summer ’26 / API 67
    • exact exception and timestamp
    • affected Processing Services classes
    • confirmation that pairing is Connected
    • CGCPSSession cache configuration
    • debug log showing the failure occurs before the callout

    Salesforce Support should also be able to confirm whether this is a known issue with cgcloud 262.x and async Processing Services session handling. 

0/9000