Data Workflows Record-Level Errors

Prev Next

Data Workflows displays errors that occur while records are processing. You can find them in the Performance Details Errors tab. This page lists errors that may occur related to the destination CRM system (Salesforce or HubSpot CRM).

This page contains a list of known errors at the time of publication. If you encounter an error that is not listed, we first recommend checking with your CRM admin team to determine if the error can be handled by your internal teams. If not, please reach out to 6sense support.

Many of the errors listed here are examples of potential errors you may receive. Detailed error messages can change based on the fields, objects, triggers, and other processes in your CRM.

Workflow-level errors may prevent a workflow from running completely. Refer to Data Workflows Workflow-Level Errors.

View record-level errors

To see the errors for records processes by Data Workflows:

  1. Go to Data Workflows > Workflows List.

  2. For the workflow, select Action > Performance Details.

  3. Select the Errors tab.

The Errors tab displays:

  • The name of the record that had an error.

  • The record’s owner.

  • The name of the node that 6sense was processing at the time of the error.

  • A description of the error.

Salesforce error message list

Error Message

Description

Account Creation

Contact Purchase

Enrichment

Push segment Names

Export Scores

DUPLICATES_DETECTED
(This error occurs when 6sense identifies the record as a new record but Validation Rules/Triggers on your Salesforce identify it as a duplicate record).

Each object in the external system has a set of fields which should be unique, if Data Workflows attempts to create record where the new values are duplicates of the old values, this record will error out

x

x

CANNOT_EXECUTE_FLOW_TRIGGER
(This error message is a general indication that there was a problem with a Flow trigger, which is a part of Salesforce’s automation capabilities. Users are advised to retry their actions, but if the problem persists, they should reach out to their Salesforce administrator for further investigation and resolution).

ERROR: CANNOT_EXECUTE_FLOW_TRIGGER:We can’t save this record because the “Lead After Create/Update” process failed. Give your Salesforce admin these details. This error occurred when the flow tried to update records:

CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: LeanData.ContinuousCleanLeadUpdateTrigger: System.LimitException: Apex CPU time limit exceeded. You can look up ExceptionCode values in the SOAP API Developer Guide. Error ID: 56968537-5135 (-706762958) look up ExceptionCode values in the SOAP API Developer Guide. Error ID: 56968537-5135 (-706762958):–

This error occurs when a pre-defined Salesforce trigger has failed.

x

x

x

x

x

Cannot Reference Converted Lead
(This error occurs when you attempt to make changes to a lead that has already
been converted into a different record type, such as a contact or opportunity.
Once a lead is converted, its information is transformed and certain
fields become locked to maintain data integrity).

This error occurs when Data Workflows is trying to perform an action on a converted lead.

x

x

x

x

x

Required fields are missing
(This error occurs when attempting to create or update a record in Salesforce,
but information in the field(LastName) is missing.
These fields are mandatory and must be filled out to successfully save or update the record).

This error occurs when Data Workflows attempts to create a record without the required fields needed to create the Account, Contact, or Lead in question.

x

x

FIELD_INTEGRITY_EXCEPTION
(This error occurs when you try to update a Picklist field
with a value outside of Picklist).

Error from Salesforce
(There’s a problem with this state, even though it may appear correct. Please select a state from the list of valid states.: Home State/Province:OtherState –)

Occurs when Data Workflows is trying to update the Salesforce object picklist field with non-picklist value.

x

x

x

x

x

We received an error from Salesforce while processing your request.
ERROR: DUPLICATE_VALUE:Maximum number of duplicate updates in one batch (12 allowed). Attempt to update Id more than once in this Api call: 0034T00000G9JQL:–

Occurs when Data Workflows is trying to update the same record multiple times within hte same request.

x

We received an error from Salesforce while processing your request.
ERROR: You don’t have the necessary permissions to change the Lead Source Field. [CONT_VR09]

Occurs when Data Workflows is trying to update the lead source field but does not have permission to do so

x

x

We received an error from Salesforce while processing your request.
ERROR: FIELD_CUSTOM_VALIDATION_EXCEPTION:You must have an account attached to a contact:–

This error is an example of when Data Workflows tries to run an operation that does not align with the Salesforce validation rules created.

x

x

x

x

x

We received an error from Salesforce while processing your request.
ERROR: DUPLICATES_DETECTED:An account with this domain already exists. Please search for it using the domain.:–

This error occurs when Data Workflows is trying to create the same record multiple times within the same request.

x

We received an error from Salesforce while processing your request.
ERROR: INVALID_FIELD:Failed to deserialize field at col 8. Due to, ‘$5B+’ is not valid for the type xsd:double:AnnualRevenue —

When application is trying to update the saleforce object annual revenue field with non-picklist value.

x

x

x

We received an error from Salesforce while processing your request.
ERROR: CompanyId should be a numeric value

When application is trying to update the salesforce object company Id field with non-numeric value.

x

x

x

We received an error from Salesforce while processing your request.
ERROR: Please select a value for Mailing Country.

Mailing country has been set mandatory in customers salesforce instance and has not been passed in the request. Similar error can come for any other mandatory field set by customer.

x

x

HubSpot CRM error message list

Error Message

Description

Company Creation

Contact Purchase

Enrichment

Push Segment Names

Export Scores

This error occurs when 6sense identifies the record as new record but Validation Rules on your Hubspot identified it as a duplicate record.
ERROR: Contact already exists. Existing ID: xxxx

Each object in external system has set of fields which should be unique, if application is trying to create object with these fields having same value as other record in the system we will get this error.

x

x

Property values were not valid
(This error occurs when you are trying to save/update
the record with values of incorrect type or the value doesn’t match the field criteria.
Please check your Mapping Profile and MAP the field(hubspot_owner_id) to the correct Hubspot field)

ERROR: Property values were not valid: [{“isValid”:false,”message”:”[email protected] was not a valid integer (for owner ID).”,”error”:”INVALID_INTEGER”,”name”:”hubspot_owner_id”,
“localizedErrorMessage”:”[email protected] was not a valid integer (for owner ID).”}]

When application is trying to update the HubSpot object picklist field with non-acceptable value.

x

x

Required fields are missing
(This error occurs when attempting to create or update a record in Hubspot,
but essential information in the id field is missing. These fields are mandatory and must be filled out to successfully save or update the record).

Each Object has certain required field defined in external system and if request are sent for objects without required fields the user will get this error.

x

x

Property values were not valid
(This error occurs when you are trying to save/update the record with values of incorrect type or the value doesn’t match the field criteria. Please check your Mapping Profile and map the field(hubspot_owner_id) to the correct Hubspot field)

ERROR: [email protected] was not a valid integer (for owner ID).

Trying to set unacceptable value to the field. In this case trying to set email in place of owner ID.

x

x

x