Loyalty Management: Data Processing Engine job fails with UNABLE_TO_LOCK_ROW and DATA_SYNC_ERROR

Work through the cause that matches the exact error text in your run history.

Cause 1: UNABLE_TO_LOCK_ROW / "unable to obtain exclusive access to this record" (DATA_SYNC_ERROR, SYSTEM_ERROR) — record locking contention.

1. Open Setup > Monitor Workflow Services > Data Processing Engine Jobs [DataProcessingEngineJobs] and open the failed run to identify the target object and record IDs reported in the failed writeback records (for example [Opportunity]).
2. Identify other automation updating the same records at the same time: go to Setup > Flows, Setup > Apex Triggers, and any other scheduled DPE definitions. List every process that writes to the target object during the DPE window.
3. Stagger the schedules so they do not overlap. In Setup > Data Processing Engine, open each conflicting definition, click Edit Schedule, and set non-overlapping start times at least 60 minutes apart.
4. In the failing definition, open the Writeback node and set Batch Size to 200 to reduce the number of records locked per transaction.
5. If a real-time trigger or flow updates the same parent record during the run, defer it: in the flow set Run Asynchronously, or schedule the trigger logic outside the DPE window.
6. Re-run the definition: in Setup > Data Processing Engine, open the definition and click Run.

Cause 2: Writeback fails because the running user lacks field access — "The given user doesn't have access to the <field> field of the target object used in the Writeback Object node."

1. Go to Setup > Data Processing Engine, open the definition, and note the running user and every field in the Writeback Object node.
2. Go to Setup > Object Manager > <Target Object> > Fields & Relationships, open each writeback target field, and click Set Field-Level Security.
3. For the running user's profile or permission set, select Visible and clear Read-Only so the user has both Read and Edit access to each writeback field.
4. Confirm the running user's profile has Edit access (object permission Edit = checked) on the target object.
5. Re-run the definition from Setup > Data Processing Engine > Run.

Cause 3: "Maximum Analytics API Calls per Hour has been exceeded" (USER_ERROR_CRMA_LIMIT_EXCEEDED) — CRM Analytics data sync API hourly limit hit.

1. In the failed run details, confirm the message reads "Current value is <n>, and the limit is 10000."
2. Reduce sync frequency: in Setup > Data Processing Engine, open each definition reading from CRM Analytics and set its schedule so no more than one large definition runs per hour.
3. Disable unneeded scheduled CRM Analytics data syncs in Analytics Studio > Data Manager > Data Sync, leaving only the connectors the DPE definition requires.
4. Move large DPE runs to off-peak hours when other CRM Analytics API consumers are idle.
5. Wait for the rolling hour to reset, then re-run the definition from Setup > Data Processing Engine > Run.

Monitoring: To be alerted to future failures, go to Setup > Data Processing Engine, open the definition, click Edit Schedule, and enter recipient addresses in the failure email notification field so you receive a message when a run fails.

Confirm the issue is resolved by re-running the DPE definition and opening Setup > Monitor Workflow Services > Data Processing Engine Jobs; the latest run shows Status = Completed with zero failed writeback records.