Loading

Salesforce NPSP: CRLP_Account_BATCH Execution Skipped Because a Previous Job is Still Running

Publiceringsdatum: Jul 15, 2026
Beskrivning

This article explains why your Nonprofit Success Pack (NPSP) Customizable Rollups batch jobs are skipped or fail to update records, and how to clear a stuck job so scheduled rollups run again.

You see the informational message "Today's scheduled npsp.CRLP_Account_BATCH batch job was skipped because a previous npsp.CRLP_Account_BATCH job was still running. The next batch job will run as scheduled. No action is required; this error is for information purposes only."

You may also receive repeated "npsp.CRLP_Batch_Base.CRLPBatchException" emails (for example the Account Hard Credit job "NPSP 01A - Customizable Rollups - Account Hard Credit" or npsp.CRLP_Contact_SoftCredit_BATCH), sometimes 4 or more per day, while rollup fields such as Total Gifts do not recalculate. Trigger conditions: a prior Customizable Rollups Apex batch job remains in Holding, Queued, or Processing state and never completes; or the Salesforce user who scheduled the job is inactive or had a license downgrade. This affects orgs using NPSP with the Household Account Model and Customizable Rollups enabled. 

Lösning

Cause 1: A previous Customizable Rollups batch job is stuck and blocks the next run.

  • Go to Setup > Environments > Jobs > Apex Jobs [AsyncApexJob].
  • . Locate any job with the class name containing [CRLP_Account_BATCH] or [CRLP_Contact_SoftCredit_BATCH] with a Status of Holding, Queued, Preparing, or Processing.
  • Copy the Job ID (the Apex Job Id value) of the stuck job.
  • Open Setup > Developer Console
  • Click Debug > Open Execute Anonymous Window.
  • Enter this line, replacing JOB_ID with the copied Apex Job Id: System.abortJob('JOB_ID');
  • Click Execute. The stuck job status changes to Aborted.
  • Go to the NPSP Settings tab > Bulk Data Processes > Batch Process Settings and confirm the checkbox [Don't Auto Schedule Default NPSP Jobs] is set to unchecked. Leaving it unchecked recreates and reschedules the default NPSP rollup jobs.
  • Return to the NPSP Settings tab > Bulk Data Processes > Customizable Rollups and click Run Rollups to launch a fresh job.

Cause 2: The user who scheduled the batch job is inactive or had a license downgrade.

  •  Go to Setup > Environments > Jobs > Scheduled Jobs [CronTrigger] and note the Submitted By user for each NPSP Customizable Rollups job (for example "NPSP 01A - Customizable Rollups - Account Hard Credit").
  • Go to Setup > Users > Users and confirm that user shows Active set to checked and holds a full Salesforce user license (not "Salesforce Integration" or a "Minimum Access - API Only" profile). A downgraded license produces "CANNOT_EXECUTE_FLOW_TRIGGER" and "Could not access field" errors; see article 005305532 for that specific downgrade scenario.
  • If the Submitted By user is inactive or restricted, delete the scheduled job from Setup > Scheduled Jobs by clicking Del next to it.
  • Log in as an active user with a full Salesforce license and the NPSP Data Import permission set.
  • Go to the NPSP Settings tab > Bulk Data Processes > Batch Process Settings, set [Don't Auto Schedule Default NPSP Jobs] to unchecked, and save to recreate the default jobs under the active user.

Confirm the issue is resolved by running the Account Hard Credit rollup manually from NPSP Settings > Bulk Data Processes > Rollup Donations Batch > Run Batch, then open Setup > Apex Jobs and verify the [CRLP_Account_BATCH] job reaches Status Completed with 0 failures. Then open an Account that received a gift and confirm the Total Gifts and related hard credit rollup fields show the expected updated values.

Knowledge-artikelnummer

005389029

 
Laddar
Salesforce Help | Article