Common sync error messages in the Salesforce Nonprofit Cloud (NPC) integration

When data doesn’t sync between GoFundMe Pro and your Nonprofit Cloud instance, you can find the reason for the error in the GFM Pro Log record. Below are known errors and how to resolve them in your instance.

After you resolve the error, submit a request with our Care team to sync the record.

Default designation isn’t configured

Full message: The org-wide default designation isn’t yet configured or is inactive. Create a default designation or mark an existing one as default, and try again.

Choose a gift designation in Salesforce and mark it as Default.

No active duplicate matching rules

Full message: Salesforce API error (400, UNKNOWN_EXCEPTION): [{"errorCode":"UNKNOWN_EXCEPTION","message":"Provide active duplicate matching rules on Account and Person Account for donor matching.

Make sure there is an active matching rule and an active duplicate rule for both Accounts and Person Accounts.

CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY

Full message: Salesforce API error (400, CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY): [{"message":"entity type cannot be inserted: Campaign","errorCode":"CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY","fields":[]}]

Review permissions for the connected integration user and their access to campaigns. They need read, create, and update access. Also, confirm that the Marketing User permission is granted.

For more information, see our recommendations on user permissions.

Record Type ID: value not valid for the entity: PersonAccount

You need to add a default record type for the integration user's profile.

Due date of Gift Commitment is not between start and end dates

Full message: Enter a due date that's on or between the Start Date and End Date of the schedule. OR Enter a date that's on or after the start date of the associated gift commitment schedule.

This error is a result of Salesforce's Fundraising Business Process API surrounding Gift Commitments and their associated Gift Commitment Schedules. Adjust the current Gift Commitment Schedule start and end dates to include the date of the transaction that is not syncing.

For example, if the transaction date is 04.30.2026, then edit the start date of the Gift Commitment Schedule associated with the Gift Commitment to 04.29.2026.

Unable to get or clone schedule

This error is a result of Salesforce's Fundraising Business Process API surrounding Gift Commitments and their associated Gift Commitment Schedules. Adjust the current Gift Commitment Schedule start and end dates to include the date of the transaction that is not syncing.

For example, if the transaction date is 04.30.2026, then edit the start date of the Gift Commitment Schedule associated with the Gift Commitment to 04.29.2026.

Gift Commitment external ID doesn't match an existing record

Full message: The provided GiftCommitment external ID doesn't match an existing record. Provide a valid GiftCommitment external ID for this object.

The Gift Commitment created by the integration was deleted. As a result, no transactions are syncing. Contact the Care team with this information for the next steps to resolve.

Required fields are missing: [Name, PaymentMethod, OriginalAmount]

Full message: Required fields are missing: [Name, PaymentMethod, OriginalAmount]"\,"errorCode\":\"REQUIRED_FIELD_MISSING\",\"fields\":[\"Name\",\"PaymentMethod\",\"OriginalAmount\"]}]"

The payout can’t sync because the associated transaction doesn’t yet exist in Salesforce. This can happen when the transaction failed to sync to Salesforce, or when it’s an ACH transaction and the payout is syncing before the transaction has settled successfully in GoFundMe Pro.

Salesforce resource not found

Full message: Salesforce resource not found (NOT_FOUND): The requested resource does not exist.

If the entry type field is PayoutTransaction, the payout can’t sync because the associated transaction doesn’t yet exist in Salesforce. This can happen when the transaction failed to sync to Salesforce, or when it’s an ACH transaction and the payout is syncing before the transaction has settled successfully in GoFundMe Pro.

If the entry type field shows a different object, these records have not been synced to the currently connected Salesforce environment yet.

Entity type cannot be inserted

Full message: Entity type cannot be inserted OBJECT"\,"errorCode\":\"CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY\",\"fields

This error occurs when a record has been synced in another Salesforce environment, but has not yet synced to the currently connected Salesforce environment. The full message will list the object type that is not syncing.

Pipeline: Error in Dependencies

A dependent record is missing, such as campaign, designation, or recurring plan. Check the related records of the Transaction and make sure they have synced to Salesforce.

donor.lastName"\,"message\":\"Specify values for the required business logic fields

The last name is missing from the Supporter's record in GoFundMe Pro, which usually happens with offline donations. Add a last name to the related Supporter record of the Transaction.

Request Refused (FUNCTIONALITY_NOT_ENABLED): This feature is not currently enabled for this user

The integration user is missing the Fundraising Access permission set. For more information, see our recommendations on user permissions.

Programmer error: cannot rollback to savepoint on another transaction

Full message: Salesforce API error (400, UNKNOWN_EXCEPTION): [{"errorCode":"UNKNOWN_EXCEPTION","message":"Programmer error: cannot rollback to savepoint on another transaction

There was an issue with Salesforce's Business Process API, and the transaction will need to be synced again.

Classy Order Comment: data value too large (max length=1000)

Edit the Transaction's order comment in GoFundMe Pro to be within the accepted limit.

Required fields are missing: _______

The field listed needs to be populated with a value. 

The integration populates the standard fields it depends on, so this error usually means an additional requirement has been added to this field in your org. Adjust or deactivate the configuration enforcing the requirement.

FIELD_CUSTOM_VALIDATION_EXCEPTION

Full message: FIELD_CUSTOM_VALIDATION_EXCEPTION): [{"message":"Please populate the ____ field.","errorCode":"FIELD_CUSTOM_VALIDATION_EXCEPTION","fields":["field api name"]

The field listed needs to be populated with a value. 

The integration populates the standard fields it depends on, so this error usually means an additional requirement has been added to this field in your org. Adjust or deactivate the configuration enforcing the requirement.

Mailing City: data value too large: ______ (max length=40)

Edit the Supporter's city in GoFundMe Pro associated with the Transaction to be within the accepted limit.

First Name: data value too large: ______ (max length=40)

Edit the Supporter's first name in GoFundMe Pro associated with the Transaction to be within the accepted limit.

Insufficient Privileges

Full message: Insufficient Privileges: <<Salesforce Record ID>>

The record identified by the Salesforce Record ID was deleted, exists in another Salesforce environment, or the integration user does not have access to it. For more information, see our recommendations on user permissions.

FIELD_INTEGRITY_EXCEPTION

Full message: FIELD_INTEGRITY_EXCEPTION): [{"message":"Enter either a Honoree Contact or Honoree Name

Edit the dedication in GoFundMe Pro on the Transaction, and add the honoree's name or the contact's name.

SF Error: Salesforce API error (400, UNKNOWN_EXCEPTION)

Full message: SF Error: Salesforce API error (400, UNKNOWN_EXCEPTION): [{"errorCode":"UNKNOWN_EXCEPTION","message":"Cannot invoke "String.isBlank()" because the return value of "industries.fundraisingops.api.input.AddressDetails.getState()" is null

There is no address for the Supporter, and the state field is blank. Add an address to the Supporter, and the transaction will need to be synced again.