MuleSoft Salesforce Connector Replay Channel Listener Stops Processing New Events after Migration to Hyperforce

Salesforce connector replay channel Listener stops processing new events after backend Salesforce instance is migrated to Hyperforce. In the logs you can observe that the replayId is invalid with error=400 from Salesforce backend with specific replayId.

CAUSE

From Mule application as Salesforce client perspective, Salesforce instance migration Preorg checklist Preorg checklist excel file item 12, Following are important.

• Pause publishing of Platform Events for a given time interval (1 hour or long enough to process all pending events in the bus) before the communicated migration window.
• Process all events that haven’t been processed up until the pause point.
• Drain the events from the Event Bus to another external system if retention of the events is needed.
• Reset your client’s storage to no longer retain and hold the last ReplayID.

Certain Salesforce maintenance activities (example: org migrations and instance refreshes) require relocating your organization to another data center or to a different hardware stack. During these operations, we are physically moving your data and running the software that serves your applications onto different hardware. Due to the distributed, asynchronous nature of our Event Bus, we are not able to migrate all events that were published prior to the org migration.

The org migration will not impact the real-time delivery of the events pre and post-maintenance; however, the 72-hour retention window for all events will not be retained. ReplayIDs uniquely identify the point in an event stream a particular event was published, and since the new location of your organization is physically different, the ReplayID values of newly published events will have no relation to events published before the migration or instance refresh.  Please see the pre  and post -checklist at the end of this knowledge article for additional actions that may be required for your Platform Events. Subscribers of platform events and change events include Streaming API (CometD) clients, empApi Lightning components, Pub/Sub API clients, event relays, Apex triggers, and flows.

Please review: Salesforce Hyperforce Migration Handling Guide