Salesforce Nonprofit Cloud: "An unhandled fault has occurred in this flow" when processing Gift Entry

Work through the causes in order. Reproduce the error as the affected user after each configuration change.

Step 1 - Read the fault email to find the failing element

The administrator who owns the flow receives an automatic fault email when the flow fails. Open this email and note the element name and the underlying error message (for example, a field-level access error, an INSUFFICIENT_ACCESS error, or a named field such as ObjectSourceCodeId or PaymentInstrumentId).

Step 2 - Capture a debug log for the affected user

1. Go to Setup > Debug Logs.

2. Under User Trace Flags, click New, set Traced Entity Type to User, and select the user experiencing the error.

3. Set the Apex Code and Workflow log levels to FINEST.

4. Have the user reproduce the error by clicking Process Gift.

5. Open the newest log and search for FLOW_ELEMENT_ERROR and INSUFFICIENT_ACCESS to identify the exact object and field causing the block.

Cause 1: Running user lacks field-level access to fields the Gift Entry flow writes.

1. Go to Setup > Object Manager > Gift Transaction (GiftTransaction) > Fields & Relationships.

2. Locate the fields named in the fault email or debug log (commonly ObjectSourceCodeId and PaymentInstrumentId).

3. Click on each field, click Set Field-Level Security, and for the affected user's profile or permission set, set the value to Visible (and clear Read-Only so the field is editable).

4. Repeat this process for any additional fields logged on Gift Transaction, Gift Commitment (GiftCommitment), Gift Commitment Schedule (GiftCommitmentSchedule), or Payment Instrument (PaymentInstrument).

5. Confirm the user's profile or permission set has Read, Create, and Edit object-level access on both Gift Transaction and Payment Instrument.

Cause 2: The error appears in a fundraising rollup automation flow after following the automatic rollups setup guide.

(Follow these steps if Step 1 identifies a rollup update element, such as a flow updating commitment-to-next-transaction values):

1. Go to Setup > Flows and open the failing fundraising rollup flow named in the fault email.

2. Click the failing element and confirm every field it reads or updates exists in your org and that the running user has Read access to those fields.

3. Verify the flow's API Version in flow settings is 55.0 or higher. Open the flow, click the version properties, and if it is lower, save it as a new version to update it.

Step 3 - Grant permission and re-run

After correcting field-level security or object access, have the affected user log out and log back in so the permission changes take effect.

Verification

Confirm the issue is resolved by having the affected user click Process Gift (or submit the Gift Entry batch) again and verifying that the Gift Transaction record saves successfully without the "An unhandled fault has occurred in this flow" message appearing.