Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Dear Community,
After Salesforce Summer '25 release in sandboxes, we started observing issues with INVALID_SESSION_ID being thrown when trying to queue any of the jobs.
The connection was established using the following knowledge article:
The Connected App wasn't modified recently. What's interesting, connection test works fine but this INVALID_SESSION_ID error is thrown after the job is run, it's just the generic exception as shown below:
java.io.IOException: [UnexpectedErrorFault [ApiFault exceptionCode='INVALID_SESSION_ID'
exceptionMessage='Invalid Session ID found in SessionHeader: Illegal Session'
extendedErrorDetails='{[0]}'
Have you observed anything similar on your end after this Summer '25 update?
There are a couple known issues updated recently but none of them was directly related to Talend:
Thank you in advance for any feedback
After discussion with Salesforce Support, it has been confirmed that it's needed to disable the following flag on the Connected App level:
"Issue JSON Web Token (JWT)-based access tokens for named users"
Hello ,
As per the supported matrix saleforce connector supports API version till 57 with the latest patch release you can refer below
And as per the salesforce as of Spring ‘25, the Salesforce API will be on version 63.0 this is not supported this could be one of the reason any possibility to create the app with lower version API and then test the job
Thank you for reply. Unfortunately, the API version is not the problem there because the connection remained with v57 and just stopped working after Summer '25 upgrade on our sandbox. We created a Connected App in Production org to ensure that exactly the same connection works fine on environment which is still on Spring '25.
To sum up:
After discussion with Salesforce Support, it has been confirmed that it's needed to disable the following flag on the Connected App level:
"Issue JSON Web Token (JWT)-based access tokens for named users"