MuleSoft Salesforce Connector: Replay channel listener processes ALL Replay IDs instead of FROM_LAST_REPLAY_ID when the Salesforce OAuth username and password are changed

This behavior is expected because the Salesforce connector uses the value provided in the 'Username' field as the ObjectStore key to store the last Replay ID.

When the username is changed, a new key-value pair is generated that does not contain the last Replay ID, resulting in the Replay option being set to 'ALL'. Consequently, the Replay channel listener will read all Replay IDs based on the Salesforce retention period, which is the last 72 hours. The increase in this load can cause latencies or craches to the application.

As a workaround, increase the worker size to provide additional CPU, memory, and I/O resources for the application to process all past Replay IDs. After processing the past Replay IDs, revert the worker size to the previous configuration.