Skip to main content
3 个回答
  1. 今天,02:42

    Hi Tory, 

     

    This is a well-documented NPSP behavior, not a bug — it happens whenever the user who originally scheduled the NPSP nightly batch jobs (rollups, recurring donations, etc.) gets deactivated (left the org, license removed, etc.). Once that user is inactive, NPSP's scheduled jobs stop running correctly and this exact error fires. 

     

    Fix: 

    1. Setup → Quick Find → Scheduled Jobs 

    2. Find any job(s) where the "Submitted By" column shows the inactive user, and click Del next to each one 

    3. Go to the NPSP Settings tab (App Launcher if it's not in your nav) 

    4. Click Bulk Data Processes → Batch Process Settings — just opening/saving this page automatically recreates the default NPSP jobs under your (currently active) user 

    5. Confirm Don't Auto Schedule Default NPSP Jobs is unchecked — if it's checked, step 4 won't auto-recreate the jobs and you'll need to reschedule manually via Setup → Apex Classes → Schedule Apex 

    6. Go back to Scheduled Jobs and confirm the jobs now show as Submitted By your active user 

     

    One job to leave alone: NPSP 00 - Error Processing runs hourly by design — don't delete/reschedule it unless it's also showing the inactive user issue. 

     

    Since this will happen again any time whoever's listed as "Submitted By" gets deactivated, it's worth having a step in your offboarding checklist to have another active admin rerun this process whenever that person leaves. 

     

    Reference:

    https://powerofus.force.com/s/article/NPSP-Edit-or-Reschedule-NPSP-Scheduled-Jobs

0/9000