Loading

Salesforce Connector Replay Channel Listener – ReplayId Persistence Fails Due to Orphaned _BACKUP Key in Object Store V2 (CloudHub 1.0)

Udgivelsesdato: Jul 9, 2026
Beskrivelse

The Salesforce Connector Replay Channel Listener persists ReplayIds to Object Store V2 to ensure that Platform Event consumption resumes from the correct position after a restart or reconnect.

During ReplayId persistence, the connector temporarily creates a backup entry (<ReplayKey>_BACKUP) as part of its update process. If the worker is terminated unexpectedly or multiple workers overlap during deployment, this backup entry may not be removed.

On the next persistence attempt, Object Store V2 detects that the backup key already exists and throws the following exception:

ObjectAlreadyExistsException: Object already exists for key <ReplayKey>_BACKUP

As a consequence:

  • ReplayId persistence fails.
  • The connector continues processing Platform Events using the in-memory ReplayId.
  • The ReplayId stored in Object Store remains unchanged.
  • After an application restart or reconnect, the connector resumes from the stale ReplayId, which can result in duplicate Platform Events being delivered.
Løsning

Workaround:
To restore ReplayId persistence:

  1. Stop the Mule application.
  2. Delete the orphaned backup key from Object Store V2.
    • Partition: StreamingObjectStore
    • Key: <ReplayKey>_BACKUP
  3. Restart the application.
  4. Verify that ReplayId persistence resumes successfully and the ReplayId stored in Object Store advances as expected.

Permanent fix:  This behavior is currently expected. A new enhancement has been requested under User Story W-22618367 to improve the handling of this scenario.

 

Vidensartikelnummer

005388736

 
Indlæser
Salesforce Help | Article