Release Notes > Connector and connectivity issues > Salesforce Connector
  

Salesforce Connector

Fixed issues

The tables in this section describe recent fixed issues for Salesforce connector in Metadata Command Center. Not all monthly releases include fixed issues.
October 2026 fixed issues
Issue
Description
SCAN-41048
When you run a Salesforce Marketing Cloud metadata extraction job, the job fails if the session connects through a child business unit. The job fails with the following error: Root business unit id was not found.
SCAN-40632
When you run a job to extract metadata of Salesforce Data 360 calculated insights whose query definition contains the DISTINCT keyword, data lineage is not generated and the following error appears in the job log: Parse error (NoViableAlt) on token: 'DISTINCT'
SCAN-38429
When you extract metadata from a Salesforce Data 360 source system with large or complex data transforms, the extraction job fails with an out-of-memory error. No metadata or lineage is generated for the affected objects.
SCAN-38303
When you extract metadata from a Salesforce source system, the extraction fails for certain standard objects in the Salesforce CRM application. Those objects do not appear in the catalog.
November 2025 fixed issues
Issue
Description
SCAN-24211
When you run a catalog source job, the generated debug logs include sensitive information.
This issue occurs if the catalog source job uses a connection configured with OAuth authentication.