Common Sync Errors & Fixes

Last updated: April 21, 2026

When the NPC integration encounters an error syncing a record, it's logged in Integration Logs within WeGive (Settings → Integrations). Each log entry includes the Salesforce error message so you can diagnose and resolve the issue.

Below are the most common errors and how to fix them.

"REQUIRED_FIELD_MISSING" — Missing Required Fields

What happened: Salesforce rejected the record because a required field was empty.

Common causes:

  • A supporter is missing a last name (required for Person Accounts)

  • A transaction is missing a status or amount

  • A GiftCommitmentSchedule is missing a TransactionPeriod or StartDate

How to fix: Check the error message for the specific field name. Update the record in WeGive with the missing data, then trigger a re-sync.

"DUPLICATE_VALUE" — Record Already Exists

What happened: WeGive tried to create a record that already exists in Salesforce, usually because of a matching external ID.

Common causes:

  • Duplicate supporter records in WeGive that map to the same Salesforce record

  • A previous sync partially completed and the retry is hitting an existing record

How to fix: Merge duplicate supporters in WeGive before re-syncing. If the Salesforce record already exists and is correct, WeGive will link to it on the next pull cycle.

"FIELD_CUSTOM_VALIDATION_EXCEPTION" — Validation Rule Blocked the Record

What happened: A Salesforce validation rule on the target object rejected the data WeGive tried to sync.

Common causes:

  • Your org has custom validation rules on GiftTransaction, GiftCommitment, Account, or other NPC objects that the synced data doesn't satisfy

  • A validation rule requires a field that WeGive doesn't populate by default

How to fix: Review the validation rule in Salesforce Setup. Either update the rule to accommodate integration-created records (e.g., add an exception for the integration user) or add a custom field mapping in WeGive to populate the required field.

"INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY" — Permission Issue

What happened: The integration user doesn't have access to a related record or object.

Common causes:

  • The integration user is missing the Fundraising Access permission set license or Fundraising User permission set

  • A record-level sharing rule is preventing access to a specific Account or Campaign

  • The integration user doesn't have access to a custom object referenced in a Flow or Process Builder

How to fix: Verify the integration user has the correct permission set license and permission set assigned. Check that org-wide defaults and sharing rules allow the integration user to access the relevant records.

"ENTITY_IS_LOCKED" — Record Is Locked

What happened: The Salesforce record is locked by an approval process or Flow.

How to fix: Unlock the record in Salesforce, or adjust the approval process to not lock records that the integration needs to update.

"STRING_TOO_LONG" — Field Value Exceeds Maximum Length

What happened: A text value from WeGive exceeds the maximum length of the Salesforce field.

Common causes:

  • Long descriptions or notes exceeding field limits

  • Custom field mappings targeting a field with a shorter length than the source data

How to fix: Check which field is causing the error and either shorten the data in WeGive or increase the field length in Salesforce (if it's a custom field).

Sync Appears Stuck

If a sync seems to be running for an unusually long time or no new data is syncing:

  1. Check Integration Logs for recent errors

  2. Check Integration Locks — a lock from a previous sync may not have released properly

  3. If a lock appears stuck, contact your WeGive CS representative to have it manually released

Do not disconnect and reconnect the integration as a troubleshooting step without contacting support first — this can cause duplicate records.

General Troubleshooting Steps

  1. Check Integration Logs first — the error message from Salesforce is almost always the answer

  2. Test in your sandbox — reproduce the issue in sandbox before making changes to production

  3. Check the integration user's permissions — most access errors trace back to a missing permission set or sharing rule

  4. Review recent Salesforce changes — new validation rules, Flows, or Process Builder automations can break sync if they weren't tested with integration-created records

  5. Contact support — reach out to your WeGive CS contact or email help@wegive.com