Overview

If your CS Catalogue is not getting published in the Full Sandbox environment and the publication status remains on 'Received' while the scheduled job stays in the 'Queued' state for hours, the issue may be due to the messaging engine being turned off. This can result in several incoming messages being stuck in the 'Correlated' status and a large number of outgoing messages stuck in 'Pending' or 'Waiting for Response' status.

Solution

Step 1: Update Older Outgoing Messages to 'Unrecoverable Error' Status

Use the following query to identify older Outgoing Messages currently in the “Pending” or “Waiting for Response” Status:

SELECT Id, CreatedDate

FROM csam__Outgoing_Message__c

WHERE csam__Status__c IN ('Pending', 'Waiting for Response')

ORDER BY CreatedDate DESC

Once you identify these messages (the ones that are older than a week), update their Status to “Integration Error” to keep them from processing once the Batch Engine starts running again, as this will probably affect the client’s other processes as well.

Step 2: Change the Status of Older Incoming Messages to 'Process Error'

Query older Incoming Messages related to recent Publications that are currently in the Status “Correlated”. (This means that these messages were not processed due to the Batch Engine being turned off. Once the Batch Engine is turned back on, these messages should get processed.)

Once you identify these messages, change their Status to “Process Error” in order to avoid problems with future publications.

Step 3: Turn on the Messaging Engine

1. Log in as the user previously used for running the messaging engine (in this case, it was the user “NextGen API User”).

2. Navigate to the following link: https://b2c--0061--csam.sandbox.vf.force.com/apex/AdminConsole

3. Press the 'Start Schedulable' button.

Step 4: Check the Outgoing Messages

Once the Batch Engine is up and running again, check if the Outgoing Messages are being processed. This may take some time as the engine has been turned off for a while.

Step 5: Republish the Catalogue

If the issue persists, try publishing the same catalogue again, ensuring that the status of both Incoming Messages for each publication is set to 'Process Error'.

Summary

To resolve the issue of the CS Catalogue not getting published in the Full Sandbox environment, ensure the messaging Batch Engine is turned on and update the status of older messages to prevent them from affecting other processes. This involves updating older Outgoing Messages to 'Unrecoverable Error' status, changing the status of older Incoming Messages to 'Process Error' and turning the Batch Engine back on.

FAQ

Why is my CS Catalogue publication stuck in 'Received' status?

This can happen if the messaging engine is turned off, causing messages to get stuck in 'Pending' or 'Waiting for Response' status.

How do I turn on the Batch Engine?

Log in as the user previously used for running the batch engine and navigate to the Admin Console. Click the 'Start Schedulable' button.

What should I do if the issue persists after following the steps?

Try publishing the same catalogue again, ensuring that the status of both incoming messages for each publication is set to 'Process Error'.