---
schema_version: "1"
id: ce989da23b060f06273ae468beff9f1f3900ce687aeb2b6bb13ad25ad0446162
title: Troubleshooting CRM Connections
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_refresh_history.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_refresh_history.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ed20096bcecf0c6c6eca247b2114cb3c78f0abe3c61c1b4aa2b64d9981285af2
description: If you have trouble with creating, refreshing, or disconnecting a Salesforce CRM data stream, see these common issues.
products:
  - Data 360
release: "264"
---
# Troubleshooting CRM Connections

If you have trouble with creating, refreshing, or disconnecting a Salesforce CRM data stream, see these common issues.

## Refresh History Object Permission Errors

The data stream **Refresh History** tab summarizes each data stream’s last 50 refresh operations including errors that occurred. Use this tab to troubleshoot errors.

A refresh can fail for these reasons:

- If you don’t enable object and field permissions during Data 360 setup, a data stream refresh can fail. Enable object and field permissions to access Salesforce CRM.
- If you delete a custom field and then add it back, a scheduled or manual data stream refresh can fail to update records or status. When you add back a field, re-enable Read access for the field.
- If you exceed the DLO to DMO mapping limit, a data stream refresh can fail to complete. Review the DMO relationship limits.
- When an incremental update or full refresh is running, adding a formula field to trigger a full refresh cancels the initial update. The update then appears as failed.
- When the following error message appears, it indicates improper permission settings.
    
    `The following fields are missing in the CRM object or you do not have permissions to read from these fields.`
    
    See [Enable Object and Field Permissions for CRM Connections](https://help.salesforce.com/s/articleView?id=data.c360_a_crm_enable_object_and_field_permissions.htm&release=264.0.0&type=5 "You can edit the Data Cloud Salesforce Connector permission set to allow ingestions of objects and fields into Data 360.").

## Streaming Errors

For a data stream to use streaming mode, grant the required permissions and satisfy all validation requirements

A data stream uses batch mode instead of streaming mode in these situations:

- The object, object type, or derived field don't support streaming. See [Object Support for CRM Data Streams](https://help.salesforce.com/s/articleView?id=data.c360_a_crm_unsupported_objects_types.htm&release=264.0.0&type=5 "When you create a Salesforce CRM data stream, the CRM connector doesn’t support the ingestion of all objects or object types from the connected CRM orgs. Use only supported objects and object types for your data stream.").
- You include batch ingested standard or custom fields in your data stream.
- You participate in the Filtering for Salesforce CRM Connector pilot and have defined a filter on a stream.
- You modified the Data Cloud Salesforce Connector permission set by adding users. When you connect to an org, the Data Cloud Salesforce Connector permission set is created and allows access to Data 360 objects and fields. This permission set is intended for the [Platform Integration User](https://help.salesforce.com/articleView?id=security_platform_integration_user.htm&language=en_US). Adding other users to this permission set prevents Data 360 from assigning the necessary permissions that are needed for streaming.
- You include custom entities in your data stream where the deployment status is **In Development** instead of **Deployed**. We recommend creating data streams only after their deployment status is **Deployed**. If you include in your data stream an entity whose status is **In Development**, the data stream automatically switches to streaming mode, but it doesn’t receive updates. To enable data ingestion, change the entity status to **Deployed** in the object manager. Note that because records that were updated while the entity was **In Development** may not sync properly, the data can be inaccurate. To avoid this inaccuracy, delete the data stream and then recreate it.

See [CRM Connector Streaming](https://help.salesforce.com/s/articleView?id=data.c360_a_crm_connector_streaming.htm&release=264.0.0&type=5 "Batch and stream processing handle data differently. Batch mode checks the data once at scheduled intervals of 10-15 minutes, and then processes and stores it in a Data Lake Object (DLO) that you can access. Streaming mode processes data with minimal latency, and reflects changes as soon as they're made in the org.") and [Create a Salesforce CRM Data Stream](https://help.salesforce.com/s/articleView?id=data.c360_a_create_crm_data_stream.htm&release=264.0.0&type=5 "Create a data stream to begin the flow of data from a Salesforce CRM data source to Data 360 for processing and unification.")

## SurveyQuestionResponse Object Ingestion Failed

Access to the `SurveyQuestionResponse` object is controlled by the `SurveyResponse` object. To ensure data ingestion for the Survey object, grant View All Records or Modify All Records permissions for the `SurveyResponse` object.

See [Enable Object and Field Permissions for CRM Connections](https://help.salesforce.com/s/articleView?id=data.c360_a_crm_enable_object_and_field_permissions.htm&release=264.0.0&type=5 "You can edit the Data Cloud Salesforce Connector permission set to allow ingestions of objects and fields into Data 360.").

## Related Object Ingestion Failures

Grant permissions on objects and related objects even if you don’t ingest the related objects into Data 360. Ingested objects that reference related objects need permissions to access the related object information and create a data stream.

See [Enable Object and Field Permissions for CRM Connections](https://help.salesforce.com/s/articleView?id=data.c360_a_crm_enable_object_and_field_permissions.htm&release=264.0.0&type=5 "You can edit the Data Cloud Salesforce Connector permission set to allow ingestions of objects and fields into Data 360.").

## Error OPERATION\_TOO\_LARGE

When the following error message appears, it indicates that one of the fields references an entity that the CRM connector can't access. To resolve this, verify that Read and View All access is granted to all the related objects.

`"[{"message":"exceeded 100000 distinct           ids","errorCode":"OPERATION_TOO_LARGE"}]"`

When an entity has more than 100,000 records with granted permissions, all records can be retrieved without issue. However, if the entity is related to another entity, the system checks if the related record also has granted permissions before returning a row. This additional query can overload the operation, as the original query expands for each related entity. To maintain performance, a hard limit is set.

For Data 360 data streams, this query always runs as the Platform Integration User. Logging in as any other user in the system can present you with a non-failing result, the problem is still permission related however and needs to be addressed in the Data Cloud Salesforce Connector permission set to proceed.

See [Enable Object and Field Permissions for CRM Connections](https://help.salesforce.com/s/articleView?id=data.c360_a_crm_enable_object_and_field_permissions.htm&release=264.0.0&type=5 "You can edit the Data Cloud Salesforce Connector permission set to allow ingestions of objects and fields into Data 360.")

## Data Stream Fails on Extraction

Extraction must succeed before ingestion begins. The data stream history panel shows when there are extraction and ingestion errors, or when there’s a successful ingestion.

See [Data Refresh Process for Extraction](https://help.salesforce.com/s/articleView?id=data.c360_a_crm_data_refresh_process_for_extraction.htm&release=264.0.0&type=5 "Data refreshes have two phases: full refresh, which replaces all destination data, and incremental refresh, which updates data between full refresh runs. You can perform both full and incremental refresh on demand. Learn about the different refresh scenarios, and the special behavior of ContentVersion and Knowledge_kav objects.").

## Data Stream Deployment Fails with a “Data Lake Object ID Cannot Be Empty” Error

When you deploy an unsupported Data 360 setup object by using [file-based metadata deployment](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/file_based.htm), the deployment leaves incomplete or orphaned records, and fails with the “Data Lake Object ID cannot be empty” error. To avoid this error, don’t include these unsupported setup objects in package.xml, destructiveChanges.xml, or change sets.

- [DataStreamDefinition](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_datastreamdefinition.htm)
- [DataSourceObject](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_datasourceobject.htm) or DataSourceObject fields
- MktDataLakeObject ([Data Lake Object](https://help.salesforce.com/s/articleView?id=data.c360_a_data_ingestion_and_modeling.htm&language=en_US))
- [ObjectSourceTargetMap](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_objectsourcetargetmap.htm)
- [MktDataTranObject](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_mktdatatranobject.htm)

## Salesforce CRM to Data 360 Data Mismatches

When integrating Salesforce CRM with Data 360, data mismatches can occur if access permissions aren't set correctly.

See [Addressing Salesforce CRM to Data 360 Data Mismatches](https://help.salesforce.com/s/articleView?id=002467417&type=1&language=en_US).

If the record count in your Salesforce CRM source doesn't match the count in your Data 360 data stream, or recently modified records aren't reflected in Data 360, this can be because you configured a periodic full refresh interval for a streaming mode data stream. In streaming mode, you can't configure the periodic full refresh interval. To sync your data, you can set a full refresh on demand by clicking the **Refresh Now** button for that stream on the **Data Streams** tab.

See [Configure Periodic Full Refresh Interval](https://help.salesforce.com/s/articleView?id=data.c360_a_crm_data_refresh_process_for_extraction.htm&release=264.0.0&type=5 "Data refreshes have two phases: full refresh, which replaces all destination data, and incremental refresh, which updates data between full refresh runs. You can perform both full and incremental refresh on demand. Learn about the different refresh scenarios, and the special behavior of ContentVersion and Knowledge_kav objects.") and [CRM Connector Streaming](https://help.salesforce.com/s/articleView?id=data.c360_a_crm_connector_streaming.htm&release=264.0.0&type=5 "Batch and stream processing handle data differently. Batch mode checks the data once at scheduled intervals of 10-15 minutes, and then processes and stores it in a Data Lake Object (DLO) that you can access. Streaming mode processes data with minimal latency, and reflects changes as soon as they're made in the org.")

## Salesforce CRM Connection Doesn't Disconnect

If you can’t remove a Salesforce CRM connection, check for system data streams. You can't edit or delete Salesforce system data streams that other applications use, such as these Digital Wallet system data streams: PF (ProvisionedFeature), TET (TenantEntitlementTransaction), or TUTM (TenantUsageTypeMultiplier). You also can't remove a connection that includes them. To remove the connection, contact Salesforce Customer Support.

See [Disconnect a Salesforce CRM Connection](https://help.salesforce.com/s/articleView?id=data.c360_a_disconnect_a_salesforce_crm_connection.htm&release=264.0.0&type=5 "When you no longer need a connection, you can delete it. After you remove a standard Salesforce CRM connection, Data 360 stops ingesting data from the connected org and deletes all the data it ingested from that org, except trust files. Data ingested from the org is removed from unified profiles the next time that identity resolution runs.").

If the record count in your Salesforce CRM source doesn't match the count in your Data 360 data stream, or recently modified records aren't reflected in Data 360, this can be because you configured a periodic full refresh interval for a streaming mode data stream. In streaming mode, you can't configure the periodic full refresh interval. To sync your data, you can set a full refresh on demand by clicking the **Refresh Now** button for that stream on the **Data Streams** tab.

See [Configure Periodic Full Refresh Interval](https://help.salesforce.com/s/articleView?id=data.c360_a_crm_data_refresh_process_for_extraction.htm&release=264.0.0&type=5 "Data refreshes have two phases: full refresh, which replaces all destination data, and incremental refresh, which updates data between full refresh runs. You can perform both full and incremental refresh on demand. Learn about the different refresh scenarios, and the special behavior of ContentVersion and Knowledge_kav objects.") and [CRM Connector Streaming](https://help.salesforce.com/s/articleView?id=data.c360_a_crm_connector_streaming.htm&release=264.0.0&type=5 "Batch and stream processing handle data differently. Batch mode checks the data once at scheduled intervals of 10-15 minutes, and then processes and stores it in a Data Lake Object (DLO) that you can access. Streaming mode processes data with minimal latency, and reflects changes as soon as they're made in the org.")

## General Considerations

Keep these considerations in mind when creating a Salesforce CRM data stream.

- The Salesforce CRM Connector doesn’t support ingestion of Big Objects from Salesforce CRM.
- The Salesforce CRM connector streaming process doesn't support data encryption with Bring Your Own Key (BYOK).
- Salesforce archives Tasks and Events that are over a year old. When ingesting data, these archived records aren’t included.
- Salesforce CRM data streams can fail due to missing field and object permissions. To download errors, go to the **Refresh History** tab of a data stream, click the error, and download the error message file.
- The number of fields and values can have an impact on refresh time and can result in timeouts.
- Enable Read permissions on related objects even if you don’t ingest the related objects into Data 360. Ingested objects that reference related objects need permissions to access the related object information and create a data stream.
- To delete a field from your connected CRM, first disable that field from Data 360 to avoid ingestion errors in data streams. See [Considerations for Data Stream Field Disablement](https://help.salesforce.com/s/articleView?id=data.c360_a_data_stream_field_deletion_settings.htm&release=264.0.0&type=5 "There are few restrictions to consider when planning to disable a data stream field.").
- You can delete the DMO only if it’s a custom object.  See [Manage Data 360 Objects and Field Mappings](https://help.salesforce.com/s/articleView?id=data.c360_a_delete_data_model_object.htm&release=264.0.0&type=5 "Edit or remove objects and field mappings associated with a data model object (DMO) or data lake object (DLO). Manage mappings and objects to ensure data accuracy and maintain the integrity of your data model.")

#### See Also

- [_Salesforce Help_: Enable Object and Field Permissions to Access Salesforce CRM in Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_enable_user_permissions_external_salesforce_org.htm&release=264.0.0&type=5 "When you connect to an org, the Data Cloud Salesforce Connector permission set is created to allow access to Data 360 objects and fields. You can edit the Data Cloud Salesforce Connector permission set to meet your organization’s needs.")
- [_Salesforce Help_: Data 360 Limits and Guidelines](https://help.salesforce.com/s/articleView?id=data.c360_a_limits_and_guidelines.htm&release=264.0.0&type=5 "Guidelines define best practice recommendations to optimize your adoption of Data 360 for best performance. Limits are boundaries beyond which features are unavailable, performance is throttled, or usage billing charges are applied. Since Data 360 is built to scale, some limits can be adjusted to meet your business needs. Work with your account executive to find a solution that meets your goals.")
- [_Salesforce Help_: Data Stream Schedule in Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_data_stream_schedule.htm&release=264.0.0&type=5 "Data streams can operate on different refresh schedules. Learn more about how and when these data streams update.")