Loading

Salesforce Connector | Mule application fails to replay platform events after Salesforce org (Hyperforce) migration

Publiseringsdato: May 7, 2026
Løsning

GOAL

A Salesforce instance migration has caused issues with event subscriptions and replay IDs. When a Salesforce instance is migrated, it can result in changes that affect event handling in your MuleSoft application. There was an error observed that says invalid replay ID on the Salesforce side, this is because the Mule application was trying to use a replay ID from the object store, which is no longer valid on the new Salesforce instance. The goal of this article is to outline the appropriate steps for recovering from the error.

PROCEDURE

As the Mule application attempts to use a replay ID stored in the object store, there are three possible scenarios with the current replay channel listener configuration:

1. The replay option is ONLY_NEW or FROM_REPLAY_ID, and the check box Replay failed events if any or resume from the last replay ID is ticked.

2. The replay option is ALL, and the check box Replay failed events if any or resume from the last replay ID is ticked.

3. The replay option is FROM_LAST_REPLAY_ID, and the check box Replay failed events if any or resume from the last replay ID is either ticked or unticked.

For scenario 1, follow the steps below:

  1. Stop the application.
  2. Delete the StreamingObjectStore Partition from the object store. For a CloudHub application, navigate to the Object Store tab.
  3. Set the replay option to ALL with the check box Replay failed events if any or resume from the last replay ID ticked in the replay channel listener. This will allow the replay channel listener to replay all events available in Salesforce following the Hyperforce migration, and store the last processed replay ID and any failed events in the object store.
  4. Redeploy the application.
  5. Set the replay option to your original choice (keep the check box Replay failed events if any or resume from the last replay ID ticked), then redeploy the application again.

For scenarios 2 and 3, follow the steps below:

  1. Stop the application.
  2. Delete the StreamingObjectStore Partition from the object store. For a CloudHub application, navigate to the Object Store tab.
  3. Start the application. This will allow the replay channel listener to replay all events available in Salesforce following the Hyperforce migration, and store the last processed replay ID (and any failed events if the Replay failed events if any or resume from the last replay ID is ticked) in the object store.

 

For more information about the replay options, refer to the following link:

https://help.salesforce.com/s/articleView?id=001115641&type=1&language=en_US

Knowledge-artikkelnummer

001117442

 
Laster
Salesforce Help | Article