Loading

Salesforce Nonprofit Cloud: Gift Commitment and rollup flows fail with row lock, CPU limit, and missing field errors

Veröffentlichungsdatum: Jul 16, 2026
Beschreibung

This article explains why automated Fundraising flows in Salesforce Nonprofit Cloud fail during record update or create operations, and what you can do to resolve each cause.

Intent: you need failing gift commitment, donor indicator, and rollup automation to complete without errors. 

Affected flows include the managed "Gift Commitment Schedule Nightly" scheduled flow, custom or standard record-triggered flows on the Gift Commitment and Gift Transaction objects, and Declarative Lookup Rollup Summary (DLRS) rollups scheduled or run on transaction creation.

Trigger conditions: the flow runs during nightly scheduled processing, on Gift Commitment or Gift Transaction insert, or when a user clicks "Manage Gift Commitment Schedules". Observed error messages include: "Error element Donor True (FlowRecordUpdate): Apex CPU time limit exceeded", "Error element Remove Monthly Donor Indicator (FlowRecordUpdate): UNABLE_TO_LOCK_ROW, unable to obtain exclusive access to this record", and "Error element Create Contact (FlowRecordCreate): FIELD_CUSTOM_VALIDATION_EXCEPTION" or a missing required field message that does not state which object holds fields such as objectsourcecodeid and paymentinstrumentid.

Affected editions: Enterprise, Unlimited, and Developer Editions with Nonprofit Cloud. Customers describe this as: "error started this morning on the test, error code Apex CPU time limit exceeded"; "the flow tries to update this record and errors unable to lock row"; and "the flow shows an error for wrong condition when I open it." This article does not cover Data Processing Engine writeback permission errors, which are addressed in a separate article.

Lösung

Identify which error you receive and follow the matching cause below. Then run the verification step.

Cause 1: "Missing required field" / FIELD_CUSTOM_VALIDATION_EXCEPTION when the flow creates or updates a record.
1. Read the invocable action error and note the field API names it lists (for example objectsourcecodeid and paymentinstrumentid). The error does not state the object, so check field-level security on both Gift Commitment [GiftCommitment] and Gift Transaction [GiftTransaction].
2. Open Setup > Object Manager > Gift Transaction > Fields & Relationships, open each listed field, click "Set Field-Level Security", and set the running user's profile or permission set to "Visible" with "Read-Only" unchecked (edit access).
3. Repeat step 2 on Setup > Object Manager > Gift Commitment > Fields & Relationships for the same fields.
4. Assign the required Fundraising permissions to the flow's running user: Setup > Permission Sets, and assign the Nonprofit Cloud Fundraising permission set that grants object and field access.

Cause 2: Flow shows a "wrong condition" error when you open it in production but not in sandbox.
1. Open Setup > Flows, open the flow, and inspect each decision or filter element for hardcoded record IDs, cross-object references, or field references that do not exist or differ in production.
2. Update any hardcoded IDs to production values, and confirm every referenced field exists and is accessible in production via Setup > Object Manager on the relevant object.

Confirm the issue is resolved by re-running the affected flow: for a scheduled flow, use Debug in Setup > Flows on a record that meets entry criteria and confirm it completes with no error; for a record-triggered flow, create or update one Gift Commitment or Gift Transaction record and verify the target record updates or creates successfully with no "UNABLE_TO_LOCK_ROW", "Apex CPU time limit exceeded", or missing-field error.

Nummer des Knowledge-Artikels

005389137

 
Laden
Salesforce Help | Article