Salesforce push errors

Some push errors are expected.

HG Insights customers very rarely have 0 push errors. There will always be an occasional conflict with another SFDC process, an occasional missing permission on certain type of records, etc.
What matters is making sure most of your records are being scored accurately, and solving impactful errors as you go!
In this article, you will find a detailed description of push errors you may encounter with Salesforce and how to solve them.

Errors which require your intervention

High Impact

Unable to create/update fields: xyz (frequent)

• What’s happening: Makdudu cannot push any new records to your Salesforce integration. Some access settings have probably changed recently.

• Resolution:

  • Have you reconnected Salesforce to HG Insights recently? Didi you make sure to use the same Salesforce user for Oauth?

  • If you kept the same user, has their permissions changed? Check by going to Profile or Permission Set as described here.

Data value too large (frequent)

• What’s happening: Some records can’t be updated because the value HG Insights is trying to push to the field (surfaced in error message) is too large.

• Resolution:

  • If value length is < 1024, the fix is yours: please update your signals fields to → Type: LongTextArea, Length: 1024, VisibleLines: 10

  • If value leength is > 1024, please reach out to support so that HG Insights can truncate its input accordingly

Required_Picklist(rare)

• What’s happening: An internal rule requiring that a field must have certain values in order to be updated prevents HG Insights from updating the record

• Resolution:

  • consider cleaning up your picklist values to match the values restricted by the following option

    

Low to Moderate Impact

Insufficient access right on object id (frequent)

• What’s happening: HG Insights is unable to push data to a specific record. This might be because some recordtypes are locked, or some specific records are locked, or some fields (for some specific records only) are locked.

• Resolution:

  Make sure HG Insights has the “Modify All” permission on Lead, Contact, Account & Opportunity objects as specified here.

  • Profile or Permission Set: Start by identifying the user's profile and any permission sets assigned to them. Navigate to the user's detail page by searching for the user in Salesforce, and review the "Profile" and "Permission Set Assignments" sections.

  • Record Type Assignments: To check the record types the user has access to, navigate to the relevant object (e.g., Account, Opportunity). Under the object’s settings, click on "Record Types." Here, you can view the profiles and permission sets associated with each record type.

  • Profile Settings: For a more detailed view of access rights, go to the user’s profile by navigating to Setup > Users > Profiles. Select the relevant profile and scroll down to the "Record Type Settings" section, where you can see the record types assigned to that profile for each object.

  • Permission Sets: If the user has permission sets, you can also check their record type access under Setup > Users > Permission Sets. Click on each permission set assigned to the user and review the "Assigned Record Types" section to see additional access.

  By combining the user’s profile and permission set information, you can determine the specific record types they have access to for each object.

No such column 'xyz' on object Contact/lead/Account (rare)

• What’s happening: HG Insights is unable to push data to the given object because it lost access to a given column or the column no longer exist.

• Resolution:

  • In Salesforce, go to Setup > Profiles.

  • Find the HG Insights user and check its related Filed-level Security.

  • In the relevant object, look for the name of the faulty field and verify that both Read Access and Edit Acces are ticked.
    

REQUIRED_FIELD_MISSING(rare)

• What’s happening: An internal rule requiring that a field must have a value in order to be updated prevents HG Insights from updating the record

• Resolution:

  • In the custom field edition page, uncheck the option to "always require a value in this field to save a record"

    

Required fields are missing: [OwnerId](rare)

• What’s happening: the HG Insights user does not see the ownerID, and the internal rule on ownerID prevents HG Insights from updating the record. It may happen for only Lead with a specific Lead Owner

• Resolution:

  • • Change permission to the HG Insights user to allow it to see Leads from this Lead Owner

Validation_xyz(rare)

• What’s happening: A validation rule prevents HG Insights from updating the record

• Resolution:

  • Ask your SFDC Admin to add an exclusion for the HG Insights user profile to not fire any validation rule when updates to records come from HG Insights.

  • Or remove the validation rule

Apex CPU time limit exceeded / CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY (rare)

• What’s happening: Salesforce CPU is shared by all processes running in the trigger code, so Apex CPU timeouts happen when several processes are running at the same time. The package that happens to be running at the moment when the time limit is exceeded gets called out on the error, regardless of how much or how little of the CPU limit it may have consumed.

  If HG Insights sync to Salesforce contributes to Apex CPU timeouts, there are other processes involved which may be consuming a much greater portion of the CPU time.

• Resolution:

  • Since HG Insights scores records by batch of 10,000 records by default, consider submitting a support ticket to our support team, asking to reduce the batch size.

  • Disable any unnecessary Process Builder or other automation flow if possible.

  • Audit the Apex code running to ensure it is efficient

Errors which don’t require your intervention

Invalid_cross_reference_key:invalid cross reference id (very frequent)

• What’s happening: HG Insights is unable to push data to the given record.

• Resolution:

  • There will always be records that have been deleted, or whose access right changed.

  • Ignore if volume is below a few thousand errors per day.

  • Else, check Profile or Permission Set as described here.

Request failed with status code 504 (frequent)

• What’s happening: Either request timeout or network issues

• Resolution:

  • This will be addressed by HG Insights’s retry logic. You don’t risk having missing scores because of this one.

  • Ignore unless volume is overwhelmingly high.

Unable to obtain exclusive access / UNABLE_TO_LOCK_ROW (frequent)

• What’s happening: Whenever a record is in the process of being created or updated in Salesforce, the record is temporarily locked by Salesforce so that no other processes will modify the record simultaneously to avoid data inconsistencies. This error indicates that Salesforce was unable to lock the specified records for the requested operation. This happens when multiple processes or users are trying to access the same records simultaneously, and Salesforce is enforcing record-level locking to maintain data integrity.

• Resolution:

  • This will be addressed by HG Insights’s retry logic.

  • If volume is very high, take a look at triggers and workflows that run on the affected records. Consider optimizing them by:

    • Moving non-critical automations to asynchronous processes (e.g., using future methods or Queueable Apex).

    • Simplifying complex logic to reduce processing time.