Resolving custom validation sync errors

Symptoms

You see a sync error in the sync-error-tool with the status code FIELD_CUSTOM_VALIDATION_EXCEPTION and a message describing which validation is blocking the record save. Examples include:

• "The email field you selected in Preferred Email is blank. Either choose a different Preferred Email, or add a value for that email field."
• "This field is required: [Field Name]."
• "You must enter a value for [Field Name] before saving."

The error message always describes the specific validation condition that failed.

Cause

When StoreConnect's sync creates or updates a record in Salesforce, all validations configured on that object run automatically. If any validation fails, the record save is blocked and a sync error is raised.

A common point of confusion is that not all custom validations appear in Setup > Validation Rules. There are three places a custom validation can live:

1. Validation rules — configured directly on the object under Setup > Object Manager > [Object] > Validation Rules. These are the most straightforward to find and edit.
2. Managed package code — installed packages from the AppExchange can include validation logic inside their Apex triggers or trigger handler frameworks. These validations are not visible in Setup > Validation Rules and cannot be edited directly.
3. Custom Apex triggers — your org may have custom Apex triggers that use addError() to enforce business rules. These behave like validation rules but are defined in code rather than configuration.

The StoreConnect sync does not have special handling for this error type. It captures the Salesforce error message and marks the Change Event as FAILED for manual review. There is no automatic retry.

Resolution

Start by reading the full error message in the sync-error-tool. The message tells you exactly what condition failed, which helps you locate the source.

Where to look

Use this checklist to find the validation that is blocking the sync:

1. Setup > Object Manager > [Object] > Validation Rules — check here first. Most custom validations are configured as validation rules.
2. Managed packages — if you cannot find a matching validation rule, the validation may come from an installed package. Go to Setup > Installed Packages and review which packages are installed on the org. Managed package validations are built into the package's Apex code and are not visible in Validation Rules.
3. Custom Apex triggers — go to Setup > Object Manager > [Object] > Triggers and review any custom triggers for addError() calls that match the error message.

Standard validation rule

If the error message matches a validation rule you can find under Setup > Object Manager > [Object] > Validation Rules:

1. Open the validation rule and review its formula.
2. Either fix the data on the record so it passes the validation, or modify the rule to allow the sync through.
3. If modifying the rule, consider adding a condition to exclude the StoreConnect Sync User so that sync operations are not blocked while keeping the rule active for manual users:
   • Add a check for the running user's profile or permission set in the validation rule formula. For example: AND( NOT($Permission.storeConnect_Sync), [your existing formula] )
4. Re-sync the affected records via the sync-error-tool.
5. Re-enable or restore the original rule if it was temporarily disabled.

Managed package validation

If you cannot find the validation in Setup > Validation Rules and the error message matches behaviour from an installed package, the validation is coming from the package's Apex code. Managed package code cannot be edited directly, but most packages provide configuration options to control their behaviour.

Start by identifying which package is responsible — review the error message and check Setup > Installed Packages.

Then work through these options in order, from most targeted to broadest:

Option 1: Check the package's configuration for a way to exclude the sync user or disable the validation

Many managed packages provide ways to control which validations run and for which users. These configuration options are typically found in two places:

• Custom settings — go to Setup > Custom Settings, find the package's settings entry (identified by the package's namespace prefix), click Manage, then Edit the org-level default. Look for checkboxes or fields that disable the specific validation mentioned in the error message.
• Custom objects — some packages store their configuration as records in a custom object rather than in custom settings. Search the App Launcher for configuration objects related to the package. These records may include fields to exclude specific users by username, allowing the sync user to bypass the validation while keeping it active for everyone else.

Refer to the package's documentation for details on where its configuration is stored and what options are available.

Option 2: Fix the data on the affected record

If you prefer not to change any package configuration:

1. Open the affected record using the Salesforce ID from the sync error.
2. Read the error message to understand what data is missing or invalid.
3. Update the record to satisfy the validation (for example, populate a required field or correct an invalid value).
4. Re-sync the affected records via the sync-error-tool.

This resolves the immediate error but does not prevent future occurrences if the sync creates or updates records with the same data pattern.

Custom Apex trigger validation

If the validation comes from a custom (non-managed) Apex trigger in your org:

1. Go to Setup > Object Manager > [Object] > Triggers.
2. Find the trigger that contains the error message text.
3. Either fix the data to satisfy the validation, or modify the trigger to exclude the StoreConnect Sync User.
4. For the Sync User exclusion pattern in Apex triggers, see resolve-flow-trigger-sync-errors which covers the same approach for Flow and trigger exclusions.
5. Re-sync the affected records via the sync-error-tool.

Verification

1. Confirm the sync error no longer appears in the sync-error-tool.
2. Open the synced record in Salesforce and verify it was created or updated correctly.
3. If you modified a validation rule, trigger, or package setting, confirm it still functions correctly for non-sync operations (manual record creation, UI updates, etc.).

Prevention

• Audit validation rules on synced objects (Account, Contact, Order) and add Sync User exclusions where appropriate.
• Check installed package settings for options to exclude the sync user or disable validations that conflict with the sync process.
• Check for managed package validations when installing new packages — test against the sync process before go-live.
• Monitor the Sync Error Tool after making changes to validation rules or installing new packages.
• Verify the running user when configuring username exclusions — check the Current User in sync error details or flow error emails to confirm the correct username to exclude. To check the configured StoreConnect Sync User, open the StoreConnect Console and go to Sync.

Related issues

• sync-error-tool
• Resolving flow and trigger blocking sync errors
• How to find and resolve sync errors