Salesforce Error with source? "The data you were trying to access could not be found""

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Over the weekend we were made aware from our Salesforce Team that an update to our lower environments were upgraded to the Spring 26 core platform. We then encountered an error where the source would not reconnect providing the error below. It briefly reconnected back to healthy but then gave me the same error again when attempting to aggregate accounts. We recently updated credentials (prior to update) and have not tried to do that again since the update. We have a rotating password through CyberArk for our Service account connected to Salesforce.

Anyone else encounter this error? It’s my first time seeing it and I can’t find anything related to this error online.

image
image536Ă—523 14.1 KB

image
image954Ă—232 6.44 KB

2

Hi @roger_dominguez

That response is a Salesforce UI “Data Not Available” HTML page, not a Salesforce API error payload. it’s almost always because the connector is landing on the wrong domain/endpoint (for example a Lightning URL) or the org is enforcing the Domain for API logins.

checks/fixes:

  1. Verify the Salesforce URL you configured in the source is an API endpoint, not a Lightning URL.
    SailPoint’s Salesforce connector doc calls out the SOAP base should be:
    https:///services/Soap/u/
    (and if “Prevent SOAP API login from https://login.salesforce.com” is enabled, you MUST use the domain-specific URL).

  2. If you’re using OAuth, also validate the token/login URL aligns with the org policy (some orgs require My Domain login URLs for API calls instead of the generic login.salesforce.com).
    Salesforce also recommends using MyDomainName.my.salesforce.com for API base URIs and not MyDomainName.lightning.force.com.

After updating the URL(s), re-save the source connection and re-run aggregation.

If it still fails, capture the Salesforce requestId shown in the error and open a case with Salesforce + SailPoint support — that requestId lets them trace the exact backend failure.