Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More

Multiple Copies of NPSP Triggers Created After Sandbox Refresh Causing Limit Errors

Publish Date: Jul 7, 2026
Description

Environment: Sandbox (Post-Refresh)
Package: Non-Profit Success Pack (NPSP)

Symptoms:

  • After a sandbox refresh, duplicate copies of every NPSP Trigger Handler record (npsp__Trigger_Handler__c) are found in the org. 
  • The sandbox hits governor limits after above Observations.
  • The sandbox becomes completely unusable
  • Running the NPSP Health Check also fails. 


Verification Query (Developer Console):
To check the number of copies for a specific trigger, run the following SOQL in the Query Editor:
Select Id, npsp__Class__c, npsp__Active__c from npsp__Trigger_Handler__c where npsp__Class__c = '<Name Of Trigger>'

Resolution
Deactivate the duplicate NPSP Trigger Handler records by setting npsp__Active__c to false via the Developer Console.

Step 1 — Open Developer Console
  1. In Lightning Experience, click the Setup gear icon (quick access menu)
  2. Click Developer Console
  3. In the Developer Console, navigate to the Query Editor tab
How to use the Query Editor in Developer Console:https://help.salesforce.com/s/articleView?id=platform.code_dev_console_tab_query_editor.htm&language=en_US&type=5

Step 2 — Run the SOQL Query for Each Trigger
  1. In the Query Editor, run the following query for each affected NPSP trigger (replace the class name as needed): Select Id, npsp__Class__c, npsp__Active__c from npsp__Trigger_Handler__c where npsp__Class__c = '<Name Of Trigger>'
  1. The results will display all copies of that trigger handler record

Step 3 — Deactivate Duplicate Records
  1. In the query results, identify the duplicate records (keep one active; deactivate the rest)
  2. Double-click on the true value in the npsp__Active__c column for a duplicate record
  3. A pencil/edit icon will appear — type false to deactivate the record
  4. Repeat for all remaining duplicate records in the result set

Step 4 — Repeat for All Affected Triggers
  • Run the same query for every other NPSP Trigger Handler class name that has duplicates
  • Deactivate all copies except one for each trigger

Step 5 — Verify
  • Once all duplicates are deactivated, attempt to run the NPSP Health Check again or any DML operation with Records (Ex: contact)
  • Confirm the sandbox is operational and no longer hitting governor limits
Knowledge Article Number

005388184

 
Loading
Salesforce Help | Article