2. Bug Fixed

Fixed Bulk V3 Recovery after Salesforce Session Expiry

Some Bulk V3 integrations could fail after the Salesforce session expired. Although the SAP CPI adapter was able to log in again, Bulk V3 processing could still use the old cached Bulk connection. Because that connection still contained the expired Salesforce session, actions such as pushing data, closing a job, or cancelling a job could fail again with INVALID_SESSION_ID.

We have been fixed by improving Bulk V3 session recovery in the SAP CPI adapter. After a Salesforce re-login, the adapter now clears the cached Bulk connection and rebuilds it with the new Salesforce session before retrying Bulk V3 actions.

This prevents repeated Bulk V3 failures after session expiry and improves the stability of SAP CPI to Salesforce integrations.

Fixed Salesforce Session-Expiry Detection in Integration V3

Integration V3 could sometimes miss an expired Salesforce session because it checked only the raw error message for INVALID_SESSION_ID. In some cases, Salesforce errors were wrapped by other exceptions, so the original session-expiry message was not always detected. When this happened, the adapter might not trigger the expected re-login and retry process, causing unnecessary integration failures.

This issue has been fixed by improving Salesforce session-expiry detection in Integration V3. The adapter now uses shared session-detection logic that can identify expired sessions from Salesforce fault types, wrapped exceptions, and messages containing INVALID_SESSION_ID.

The same improved detection is also used by Normal Integration and Raw Content Integration V3, making session recovery more consistent across integration flows. This fix improves reliability when Salesforce sessions expire and allows the adapter to re-authenticate and retry processing correctly.