Accelerate the Value of Data

Salesforce Connector API Error Codes

Relate the Salesforce API error codes with the error messages and possible solutions to resolve the issues.

Common Error Codes

CodeMessageFix
1000Full authentication is required to access this resourceProvide bearer token in the request header.
1010This endpoint is forbidden for current userUser does not have appropriate Reltio permission to work with {tenantId}. The Reltio customer with ROLE_ADMIN_CUSTOMER role, will grant user access using the User Management application in Console with details such as environment, tenant ID, and endpoint.
1020Invalid request, tenant {tenantId} is forbidden for current userUser does not have appropriate Reltio permission to work with {tenantId}. The Reltio customer with ROLE_ADMIN_CUSTOMER role, will grant user access using the User Management application in Console with details such as environment, tenant ID, and endpoint.
103010 mb request limit exceededRequest body is too large. Split data into smaller batches. If required, contact Reltio support team.
1040Request body is not JSON ArrayEnsure that the request body is in JSON Array format starting with '[' and ending with ']'.
1050Request body is not JSONEnsure that the request body is in JSON Array format starting with '{' and ending with '}'.
1060Required parameter '{parameterName}' is missingProvide the {parameterName} in your request.

Configuration API Error Codes

CodeMessageFix
1100Profile '{profileName}' does not existCreate a new profile with {profileName} before accessing the API. For more information, see Adding a Profile
1110Tenant {tenantId} is not registered.Register the {tenantId} before accessing the endpoint.
1120Tenant {tenantId} is already registeredIndicates that the tenant is already registered and there is no need for additional steps.
1130Profile deletion failedProfile is not deleted. Contact Reltio support team and provide details.
1140Configuration must be specified for new profileProvide configuration (Reltio and Salesforce connection information) for the new profile.
1150Mapping must be specified for new profileProvide mapping for the new profile.

For more information, see Sync and Mapping Errors.

1160Required section "reltio" is missing in profile.Provide Reltio section in profile configuration.
1170Required field '{fieldName}' is missing in '{sectionName}' section.Provide {fieldName} in the {sectionName} of the mapping configuration.
1180Field '{fieldName}' is missing in '{sectionName}' section.Provide {fieldName} in the {sectionName} of the mapping configuration.
1190The reltio.tenantUrl value does not matches to https://{environment}.reltio.com/reltio/api/{tenant}.Fix the tenantUrl attribute in the profile configuration.
1200The initial tenant name does not correspond to reltio.tenantUrl.Fix the request URL by providing the correct tenantID. It should be same as in profile configuration.
1210Tenant {tenantId} not found{tenantId} does not exist in the environment specified in the profile configuration. Contact Reltio support team to provide the tenant with specified Id.
1220Not authorized Reltio userUser credentials provided in profile configuration are wrong. Try to fix or delete them, so that the default service user will be used by the Salesforce Connector.
1230Authentication failed. Please check username, password, authUrl and authTokenUser credentials provided in profile configuration are wrong. Try to fix or delete them, so that default service user will be used by Salesforce Connector.
1240Required section 'salesforce' is missing in the profile.Provide a mandatory salesforce section in the profile configuration.
1245Reporting email is not validProvided email string is not a valid email.
1250Wrong user value [{username}] formatFix the Salesforce user {username}. It must be in email format.
1260Wrong namespace value [{namespace}] formatFix the Managed Package namespace value. To get the correct name of Manage Package namespace, log in to Salesforce, navigate to Setup > Installed Packages > Reltio Connected Customer Data For Salesforce and check the namespace prefix attribute.
1270Connection to Salesforce was failed.Verify the username, password, security token, loginUrl in the Salesforce connection section of the profile configuration.
1275Connection to custom merge failedVerify whether URL for Custom Merge Service is correct. Make sure the required APIs are implemented.
1280Profile '{profileName}' already uses the same Salesforce login URL and usernameProvide another Salesforce user credential for the new profile as the username specified is already registered in another profile.
1290Default SQS settings are absent in global configuration.Salesforce Connector service is not configured properly and hence the profile cannot be stored. Contact Reltio support to fix the issue.
1300Tenant registration API is deprecated. Use the profile registration API instead.Use profile registration endpoint instead of the tenant registration.
1310Metadata for tenant '{tenantId}' is not available.Tenant {tenantId} is not configured properly. Contact Reltio support to provide the configured tenant.
1320Metadata for sObject type '{sObjectType}' is not available.Check for typo in the sObject Type name in mapping. Fix the typo and try to POST the mapping again.
1330Cannot retrieve L3 configuration for tenant: {tenantId}There are issues in the tenant metadata retrieval. Check the tenantUrl in profile configuration. If everything is correct, then contact the Reltio support team.
1340Cannot retrieve sobject metadata from Salesforce for tenant {tenantId}There are issues in Salesforce sObject metadata retrieval. Check the Salesforce connection attributes in the profile configuration. Check for the correctness of sObject Type name that is provided in the mapping.
1350Cannot retrieve record types from Salesforce for tenant {tenantId}Check if the record types are enabled in your Salesforce Organization for the specified sObject type.
1355'{Reltio_Sync__c}' table is not accessible. Please check that SFDC managed package is installedCheck the managed package is installed in Salesforce organization.

Check if the connector service user has access to Reltio_Sync__c table.

Preview Mapping API Error Codes

CodeMessageFix
1360Profile configuration for tenant '{tenantId}' not foundCreate the profile configuration with mapping before accessing the preview mapping endpoint.
1370Wrong query parameters: {params}Check if there are typos in the sObject and recordTypeId request parameters.
1380Requested object not found in mappingAdd mapping for sObject using the configuration API before using the preview mapping endpoint.

Queue Cleaning API Error Codes

CodeMessageFix
1400From SFDC To Reltio queue clearing is not supported via API. Please try to use Control Panel in your SFDC InstanceLogin to your Salesforce Organization. Launch Reltio Connected Customer Data For Salesforce application. Navigate to Data Restore > Remove Sync Events and click the Clear button.
1410Sync direction is not defined. Please use to_salesforce or to_reltio in the query pathSpecify the direction of synchronization in your request.

Enable/Disable Synchronization API Error Codes

CodeMessageFix
1420Parameter 'enabled' must be true or false.Check the enabled query parameter.
1430Error when generate SFDC Package ConfigurationContact the Reltio support team.

Mapping Validation API Error Codes

CodeMessageFix
2000Provided mapping is not a JSON arrayMapping must start with '[' and end with ']'.
2010Provided mapping contains more than one SFDC sourceRemove the odd Salesforce source.
2020Attribute 'isActive' must have boolean value. Possible values: 'true|false'Fix the isActive attribute in mapping.
2025"Attribute 'processMerge' must have boolean value. Possible values: 'true|false'".Set the value for processMerge attribute as true or false.
2026"Attribute 'customMerge' must have boolean value. Possible values: 'true|false'"Set the value for customMerge attribute as true or false.
2030Field 'deleteRelatedObjects' must have boolean value. Possible values: 'true|false'Fix the deleteRelatedObjects attribute in mapping.
2040Attribute 'type' has '{sObjectType}' value. Salesforce organization does not have this object typeRemove the mapping for {sObjectType} or fix any typos in the type name.
2050Attribute 'recordTypeId' has '{recordType}' value. Salesforce object does not have this record type

Fix the {recordType} in mapping. To get a full list of available record types, log in to Salesforce, open Developer Console and execute SOQL query:

SELECT Id, Name, SobjectType
                      FROM RecordType where isActive = true
2060Field 'attributeMapping' is not an arrayFix the attributeMapping value in mapping.
2070Field 'relatedObjects' is not an arrayFix the relatedObjects value in mapping.
2080Field 'relations' is not an arrayFix the relations value in mapping.
2090Attribute 'sfdcSource' has '{sourceValue}' value. L3 configuration does not have this source in the sources list{sourceValue} is absent in Reltio L3 configuration. Create new one with same name or use an existing name. To check list of available sources, navigate to Reltio Console application Data Modeler.
2100Attribute 'sfdcSource' has SFDC source '{sfdcSource}' that is used in another profileUse another source in mapping. Only single source per profile is allowed.
2110Attribute 'reltioObjectType' has '{reltioObjectType}' value. L3 configuration does not have this entity type in the entityTypes list{reltioObjectType} is absent in Reltio L3 configuration. Create new one with same name or use an existing name. To check the list of available entity types navigate to Reltio Console application Data Modeler.
2120Attribute 'reltioObjectType' has '{relationType}' value. L3 configuration does not have this relation type in the relationTypes list{relationType} is absent in Reltio L3 configuration. Create a new one with same name or use an existing one. To check the list of available relation types navigate to Reltio Console application Data Modeler.
2130Sync object '[{syncObject}]' duplication found: {syncObject}Remove duplicated {syncObject} section from attributeMapping section.
2140Duplication found in related objects: {relatedObject}Remove the duplicated {relatedObject} section from relatedObjects section.
2150Attribute 'relationType' has '{relationType}' value. L3 configuration does not have this relation type in the 'relationTypes' list{relationType} is absent in Reltio L3 configuration. Create new one with same name or use an existing name. To check list of available relation types navigate to Reltio Console application Data Modeler.
2160Attribute 'relation' must be true for relation typesSet the relation attribute to true.
2170Attribute 'startObjectType' must be specified for relation typesSpecify the startObjectType for all relation types in mapping.
2180StartObjectType {StartObjectType} is not mappedProvide an appropriate type for {StartObjectType}.
2190StartObjectType {StartObjectType} does not match or extend startObject type defined in relation metadata '{relationMetadata}'Provide the correct type for {StartObjectType}. To check the relation details, navigate to Reltio Console application Data Modeler.
2200Attribute 'endObjectType' must be specified for relation typesSpecify theendObjectType for all relation types in the mapping
2210EndObjectType {EndObjectType} is not mappedSpecify the endObjectType for all relation types in the mapping
2220StartObjectType {StartObjectType} does not match or extend endObject type defined in relation metadata '{relationMetadata}'Provide the correct type for {StartObjectType}. To check relation details navigate to Reltio Console application Data Modeler.
2230StartObject type '{StartObjectType}' is not present in mappingProvide the mapping for {StartObjectType} to use it in relation.
2240StartObject mapped to Salesforce type '{sObjectType1}'. It does not match with parent object type {sObjectType2}Replace the {sObjectType1} with {sObjectType2} in mapping to comply Salesforce metadata.
2250EndObject type '{EndObject1}' it does not match to current Salesforce object type '{EndObject2}'Replace the {EndObject1} with {EndObject2} in mapping to comply Salesforce metadata.
2260Attribute 'startField' of 'sobject' must be specified for relation typesProvidethe sobject startField attribute in relation mapping.
2270Attribute 'endField' of 'sobject' must be specified for relation typesProvide the sobject endField attribute in relation mapping.
2280StartObject entity type '{entityType}' cannot be mapped to sobject type '{sObjectType}'Replace {entityType} with appropriate entity type. Entity type should match or extend base entity type specified as Start Object of relation type. To check relation details navigate to Reltio Console application Data Modeler.
2290EndObject entity type '{entityType}' cannot be mapped to sobject type '{sObjectType}'Replace the {entityType} with appropriate entity type. Entity type should match or extend the base entity type specified as End Object of the relation type. To check relation details, navigate to Reltio Console application Data Modeler.
2300Required sobject field '{field}' is missing in 'attributeMapping'Specify the required {field} for appropriate sObject Type in attribute mapping. Without specifying the required field, create events cannot be processed from Reltio to Salesforce.
2310Required field '{field}' is missingSpecify the {field} in mapping.
2320Attribute '{attribute}' does not exist in Salesforce object '{sObject}'Check for typos in the {attribute} specified for the {sObject} attribute mapping.
2330Attribute '{attribute}' is ExternalID field and cannot be used in Reltio -> Salesforce mappingRemove the {attribute} from attribute mapping, as it is read only.
2340Sobject field '{field}' is read-only field and cannot be used in Reltio -> Salesforce mappingRemove {field} from attribute mapping, as it is read only.
2350Attribute '{attribute}' does not exist in Reltio object '{entity}'Check for typos in the {attribute} in {entity} mapping. Use the Data Modeler Reltio Console application to verify existing attribute names.
2355Attribute '{0}' must have string valueCheck if the {attribute} in {entity} mapping has string value.
2360Attribute 'relationType' has '{relationValue}' value. L3 configuration does not have this relation type in the 'relationTypes' listRemove the {relationType} from mapping. Check the list of available relations in Data Modeler Reltio Console application.
2370Attribute 'relationType' has '{relationValue}' value which is already used in custom object relation mappingRemove the {relationValue} from relations mapping.
2380Attribute 'sfdcAttrName' has '{attrValue}' value. This field is not found in Salesforce metadataRemove the {attrValue} from attribute mapping. Check for the list of available sObject fields in Salesforce.
2390Attribute 'sfdcAttrName' has '{attrValue}' value. This field cannot contain a reference to another objectFix the {attrValue} to appropriate value following the Salesforce Connector Mapping documentation.
2400Attribute '{attr}' does not exist in Reltio object '{entityType}'Remove {attr} from attributes mapping. Check the list of available {entityType} entity attributes in Data Modeler Reltio Console application.
2410Attribute '{attr}' has 'Reference' type. Attribute mapping must have 'sobject' or 'compoundFieldName'Fix {attr} to correct sObject type or compoundFieldName. Check the list of available sObject fields in Salesforce.
2415Attribute 'forceRefEntityMerge' must have boolean value. Possible values: 'true|false'Fix the forceRefEntityMerge attribute in mapping to correct the boolean value.
2420Attribute '{attr}' does not exist in Salesforce object '{sObject}'Remove {attr} from related objects mapping. Check the list of available sObject fields in Salesforce.
2430Attribute 'relationType' has '{relationType}' value. L3 configuration does not have this relation type in the 'relationTypes' listRemove {relationType} from mapping. Check the list of available relations in Data Modeler Reltio Console application.
2440Attribute '{attr}' does not exist in Reltio object '{entityType}'Remove {attr} from attributes mapping. Check the list of available entity attributes in Data Modeler Reltio Console application.
2450Attribute '{attr}' does not exist in Salesforce object '{sObject}' in childRelationshipsRemove {attr} from related objects mapping. Check the list of available sObject fields in Salesforce.
2460Filter '{filter}' has wrong format or function type is not supportedFix the {filter} expression by following the Mapping Filter documentation.
2470Function '{fnName}' has wrong formatFix the function {fnName} format by following the Mapping Functions documentation.
2480Function '{fnName}' is not supportedRemove the function {fnName} from mapping and use a supported function by following the Mapping Functions documentation.
2490Function '{fnName}' has no argumentsProvide appropriate arguments for the function {fnName} by following the Mapping Functions documentation.
2500Attribute '{attr}' in function '{fnName}' does not exist in Reltio object '{entityType}'Fix the expression to use the appropriate entity attribute.
2510Attribute '{attr}' in function '{fnName}' does not exist in Salesforce object '{sObject}'Fix the expression to use appropriate sObject field.
2520Function '{fnName}' must have one parameterSpecify a parameter for the function {fnName}.
2530Attribute '{attr}' in function '{fnName}' does not exist in Reltio object '{entityType}'Fix the expression to use appropriate entity attribute.
2540Attribute '{attr}' in function '{fnName}' does not exist in Salesforce object '{sObject}'Fix the expression to use appropriate sObject field.
2550Function '{fnName}' must have two parametersSpecify two parameter for the function {fnName}.
2555Function '{0}' must have two or more parametersSpecify two or more parameter for function {fnName}.
2560Function '{fnName}' argument should be a numberFix the function {fnName} argument. It should be a number.
2570Function '{fnName}' must have {paramsQuantity} parametersSpecify the {paramsQuantity} parameters for the function {fnName}.
2575Function '{0}' cannot be used after function 'split'.Do not use the equalsLookup or notEqualsLookup functions in a sequence of functions if the "split" function was previously used.
2580Reltio type '{reltioType}' ({entityType}) not convertible to sf type '{sfType}' ({sObject})

Change the attribute type in Reltio or the field type in Salesforce to be compliant. If this is not possible, then use the expression to overcome limitation (example: “=source(attribute)“)

2590Sf type '{sfType}' ({sObject}) not convertible to Reltio type '{reltioType}' ({entityType})

Change the attribute type in Reltio or the field type in Salesforce to be compliant. If this is not possible, then use the expression to overcome limitation (example: “=source(field)“)

Debugging API Error Codes

CodeMessageFix
3000Object type is not specifiedSpecify the object type in request.
3010Mapping for '{sObject}' and recordTypeId '{recordType}' and tenant '{tenantId}' not foundCreate the mapping for {sObject} {recordType} for {tenantId} if it is expected.
3020Mapping for '{sObject}' and tenant '{tenantId}' not foundCreate the mapping for {sObject} for {tenantId} if it is expected.
3030No mapping found for type '{sObject}' and record type '{recordType}'Create the mapping for {sObject} and {recordType} if it is expected.

Custom Logic API Error Codes

CodeMessageFix
4000Incorrect custom logic formatFix the custom logic script format by following the Custom Logic documentation.
4010{hookName} is not supportedRemove the {hookName} from custom logic script as it is not supported.
4020{value} is not a FunctionFix the {value} to comply with the JavaScript Function format.
4030Error occurred during module generation: {details}Verify the custom logic script content for errors which occur due to script compilation. If no issues are found, then contact the Reltio support team.
4040Custom Logic is not configured for '{profileName}' profileCreate custom logic script and post it if you are expecting one. If not, you may ignore the error.

Events API Error Codes

CodeMessageFix
5000Statistics is globally disabledContact Reltio support team to enable statistics in Salesforce Connector service.
5010Statistics is disabled for {tenantId}Update the profile configuration for {tenantId} by enabling statistics (you need to remove statistics section and not to disable events collection).
5020[{wrongDatetimeValue}] not a DatetimeFix the {wrongDatetimeValue} to correct the format by following the Events API documentation.
5030[{wrongValue}] wrong {paramName}, possible values: [{possibleValues}]Fix the {wrongValue} for {paramName} to one of the values from {possibleValues}
5040[{paramName}] is mandatoryProvide the {paramName} in request.
5050[{wrongValue}] is not valid value for [{paramName}]Fix the {wrongValue} for {paramName} by following the Events API documentation.
5060[{wrongUri}] is not uriFix the {wrongUri} to appropriate Reltio entity URI format.
5070Statistics is not available for AWS SFDC Connector Instances.When the functionality is available, it will be implemented.

Connected Organizations API Error Code

CodeMessageFix
6000Cannot get organizations connected to Reltio tenantContact the Reltio support team to get details about the error.

Synchronization API Error Codes

CodeMessageFix
8000Should be array data with size no more than {size}.Check the request body in JSON Array format and decrease size of the data, if it exceeds the limit.
8010Reltio type '{entityType}' does not exist in the mappingProvide the mapping for {entityType}.
8020Merge is switched off for Reltio type '{entityType}'Update the mapping for {entityType} to enable merge.
8030Merge is not supported for Reltio type '{entityType}'Update the mapping for {entityType} to support merge.
8040Incoming data should be an ObjectFormat the request body as JSON.
8050Incoming data should be valid JSON data.Format the request body as JSON.
8060No uri found for type: '{type}'.Specify other reltio type to perform synchronization.
8070'{uriValue}' is not valid uriFix {uriValue} to appropriate Reltio entity URI format.

Monitoring API Error Codes

CodeMessageFix
9010Parameter 'from' should have 'YYYY-MM-DDTHH:mm:ss.sssZ' formatFix the from query parameter to appropriate format.
9020Parameter 'to' should have 'YYYY-MM-DDTHH:mm:ss.sssZ' formatFix the to query parameter to appropriate format.
9030Maximum time range '{timeRange} days' exceededDecrease the time range in request.
9050Parameter 'enabled' must be 'true' or 'false'Fix the enabled query parameter value.
9060Monitoring API is not available for AWS SFDC Connector Instances.When the functionality is available, it will be implemented.

Salesforce Connector Synchronization Process Error Codes

CodeOld CodeFlow DirectionMessageCauseFix
CNR_3500CNR_E211Reltio → SalesforceEntity not processed
Connector logs this message when the entity data synchronization process from Reltio to Salesforce fails on any of these steps with application error:
  • Getting data from Reltio
  • Posting data to Salesforce
  • Callback data to Reltio
Applicable for these event types:
  • ENTITY_CREATED
  • ENTITY_CHANGED
  • ENTITY_REMOVED
  • ENTITIES_MERGED
Connector will automatically retry requests to Salesforce if there is an internal timeout (for example, ETIMEDOUT) or network issue until the retry limit is reached (default = 4). This log entry is created only after all attempts are exhausted, which means that this event/entity was not synchronized.

Understand the root cause of the problem on Reltio or Salesforce side and fix it.

If requests are failing due to ETIMEDOUT more than expected, ensure that ALL Connector IP addresses (from all pods) are added to whitelist.

Additionally, check Salesforce limits and concurrency capacity to deal with API requests to match the predicted data load (Salesforce Developers).

Manually re-sync the entity or generate a new Reltio event.

CNR_3501CNR_E211Reltio → SalesforceEntity not processed due to data error Connector logs this message when the entity data synchronization process from Reltio to Salesforce fails on any of these steps with data error:
  • Getting data from Reltio
  • Posting data to Salesforce
  • Callback data to Reltio
Applicable for event types:
  • ENTITY_CREATED
  • ENTITY_CHANGED
  • ENTITY_REMOVED
  • ENTITIES_MERGED

Examples of functional/data errors (not complete list):

  • FIELD_CUSTOM_VALIDATION_EXCEPTION
  • MALFORMED_ID
  • INVALID_CROSS_REFERENCE_KEY
  • STRING_TOO_LONG
  • REQUIRED_FIELD_MISSING
  • STORAGE_LIMIT_EXCEEDED
  • CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY
Understand the root cause of the problem on the Salesforce side and fix it.

Manually re-sync the entity or generate a new Reltio event.

CNR_3504N/AReltio → SalesforceRelation not processed
Connector logs this message when the relation data synchronization process from Reltio to Salesforce fails on any of these steps with application error:
  • Getting Reltio event and storing to Database
  • Getting data from Reltio
  • Posting data to Salesforce
  • Callback data to Reltio

Applicable for event types:

  • RELATIONSHIP_CREATED
  • RELATIONSHIP_CHANGED
  • RELATIONSHIP_REMOVED

Connector will automatically retry requests to Salesforce if there is an internal timeout (For example, ETIMEDOUT) or network issue until the retry limit is reached (default = 4). This log entry is created only after all attempts are exhausted, which means that this event/entity was not synchronized.

Understand the root cause of the problem on Reltio or Salesforce side and fix it.

If requests are failing due to ETIMEDOUT more than expected, ensure that ALL Connector IP addresses (from all pods) are added to whitelist.

Additionally, check Salesforce limits and concurrency capacity to deal with API requests to match the predicted data load (Salesforce Developers).

Manually re-sync the entity or generate a new Reltio event.

CNR_3505N/AReltio → SalesforceRelation not processed due to data errorConnector logs this message when the relation data synchronization process from Reltio to Salesforce fails on any of these steps with data error:
  • Getting data from Reltio
  • Posting data to Salesforce
  • Callback data to Reltio
Applicable for event types:
  • RELATIONSHIP_CREATED
  • RELATIONSHIP_CHANGED
  • RELATIONSHIP_REMOVED

Examples of functional/data errors (not complete list):

  • Relation type not supported
  • Failed to load relation
  • Start object entity not found
  • End object entity not found
  • Start object entity filtered out, uri:
  • End object entity filtered out, uri:
  • Failed to synchronize start object entity:
  • Failed to synchronize end object entity:

Understand the root cause of the problem on Reltio or Salesforce side and fix it.

Manually re-sync the relation or generate a new Reltio event.

CNR_3510CNR_W004Reltio → Salesforce

Event processing has reached timeout.

Retry events processing will be executed.

Connector logs this message when the connector is unable to finish the data synchronization process (which can include a batch of items) from Reltio to Salesforce within the pre-configured timeout (default is 5 min).

A data synchronization process is composed of the following steps:
  • Getting data from Reltio
  • Posting data to Salesforce
  • Callback data to Reltio

If the connector is unable to complete these steps, it will log this error message and automatically retry the process from the beginning for the events that were not completed.

Repeated log messages for the same event may indicate that part of the process is taking more time than anticipated. This may be due to slowness of the involved systems, number of retries, applicational, or data issues.

We recommend that you use the trackID to take a look at any related log entries and understand any possible errors.

For example, connector post callback for the entity with thousands of attributes and platform is unable to process it and send a response.

CNR_3600CNR_E220Salesforce → ReltioSalesforce event not processed

Connector logs this message when it is unable to finish the data synchronization process from Salesforce to Reltio due to an application error.

A data synchronization process is composed of the following steps:
  • sObject to Reltio entity conversion
  • Post data to Reltio
Connector will automatically retry the data synchronization process if it failed for any reason (by default there are four retry attempts).
Possible errors:
  • Connector didn't get a response from Reltio
  • Synchronization process didn't finish within timeout (5 minutes by default)
Examples:
  • Timed out after 300000 ms
Applicable for event types:
  • created
  • updated
  • deleted

Understand the root cause of the problem on Reltio side and fix it.

Manually re-sync the Salesforce event.

CNR_3601CNR_E220Salesforce → ReltioSalesforce event not processed due to data error

Connector logs this message when it is unable to finish the data synchronization process from Salesforce to Reltio due to data error.

A data synchronization process is composed by the following steps:
  • sObject to Reltio entity conversion
  • Post data to Reltio
Connector will automatically retry the data synchronization process if it failed for any reason (by default there are four retry attempts).
Possible errors:
  • Mapping not found
  • Unknown event type
  • Response with the error in the body from Reltio
Examples:
  • Entry contains an object that is too large to save it.
  • Relation with the same crosswalk(s) but different start/end objects already exists.
  • Invalid relationship endpoint type specification.
  • An entity of another type with the same crosswalk was found.
  • Message type contact not found in mapping.
  • Entity [CrosswalkTO {type: configuration/sources/Salesforce, sourceTable: Account, value: 0010900002EKCCfAAP}] specified in relationship as start or end entity not found.
Applicable for event types:
  • created
  • updated
  • deleted

Understand the root cause of the problem on Reltio side and fix it.

Manually re-sync the Salesforce event.