Salesforce NPSP: recurring "error insert failed" and "error delete failed" NPSP error notification emails

Work through the cause that matches the error text in your notification email.

Cause 1: You want to see or stop the recurring NPSP error notification emails.
1. Go to Setup > Installed Packages, and open the NPSP Settings tab (App Launcher > NPSP Settings).
2. Select System > Error Notifications.
3. In [Error Notification Recipients], review who receives the emails. To route them to a single mailbox, set the value to a specific Chatter group or a single System Administrator user instead of "All Sys Admins".
4. Confirm [Store Errors] is set to "Yes" so every failure is logged to the NPSP Error object [npsp__Error__c] even when the email is suppressed.
5. To read the full stack trace of each notification, open App Launcher > Error Logs (or the [Error__c] tab) and open the most recent record. The [Full Message] field [npsp__Full_Message__c] contains the exact failing row ID and exception.

Cause 2: The email reads "Error Type: Batch Apex error" or "Error insert failed / exception on row" during nightly jobs.
1. In NPSP Settings > Bulk Data Processes, note which job is failing (Rollups, Address Verification, or Recurring Donations).
2. Open the Error Log record and read the [Full Message] to find the failing record ID and the exception class.
3. If the message contains "CANNOT_EXECUTE_FLOW_TRIGGER" or "Could not access field", the user who scheduled the batch job has a restricted license or profile. Go to Setup > Scheduled Jobs, delete the failing NPSP schedulable jobs, then reschedule them while logged in as a user with a full Salesforce license and "System Administrator" profile via NPSP Settings > Bulk Data Processes > Schedule Jobs.
4. If the message contains "UNABLE_TO_LOCK_ROW", a concurrent process is locking the same record. Reschedule the failing NPSP batch job to a time when no other automation runs, and stagger overlapping scheduled jobs by at least 30 minutes.

Cause 3: The email reads "Error Type: Future method error" or "Error delete failed... entity is deleted", or you get a script error using Manage Household to separate Contacts.
1. This is thrown by the NPSP TDTM Household framework when a related Contact, Address, or Household record was already removed. Open App Launcher > Error Logs and read the [Full Message] for the row ID in "exception on row with id ...".
2. If the failing message references "npsp.HH_..." or "npsp.ADDR_Contact_TDTM" and involves a NullPointerException, open NPSP Settings > People > Household Account, and confirm the Contact you are separating has a populated [Account Name] and no orphaned NPSP Address [npsp__Address__c] records pointing to the old Household.
3. As a temporary measure to stop the recurring failure while you clean data, go to NPSP Settings > People > Household Account and set [Household Object Rules] to "No Contacts", then create Household records manually for affected Contacts. Re-enable your prior setting after cleanup.
4. Delete the specific orphaned or duplicate record identified by the row ID before retrying the Manage Household action.

Cause 4: The notification is about a Pledge/tax-receipt run showing "all records notice" with no error message text.
1. The blank-body notification means NPSP logged a failure but the stack trace was truncated. Set NPSP Settings > System > Error Notifications > [Store Errors] to "Yes" and reproduce the run.
2. Open the newly created Error Log record and use its [Full Message] to identify the failing record, then correct that record's data (typically a missing required field or a validation rule blocking insert).

Confirm the issue is resolved by re-running the affected NPSP batch job (or repeating the Manage Household separation) after correcting the flagged record, then verifying no new record is created in App Launcher > Error Logs and no new NPSP error notification email arrives within the next scheduled run.