What should a nonprofit admin consider if NPSP batch jobs are taking longer to complete?

When considering why batch jobs in NPSP might take longer to complete, it's important to recognize the impact of automation tools like Process Builder on system performance. When a new Process Builder process is activated, it can add additional logic and steps that need to be executed during a batch job. This complexity can lead to increased processing time because the system must work through the new process every time the batch job runs.

In contrast, adding a standard roll-up summary field or a customizable rollup will also affect performance, but these changes typically relate directly to how data is aggregated, rather than introducing new logic pathways that the batch processing has to follow. Similarly, adding a node tree to the role hierarchy could alter permissions and access layers within the organization, but this doesn't necessarily add processing calculations that would impact batch job execution time as directly as activating a new Process Builder process.

By focusing on the effect of activated automation like Process Builder, one can better understand the delays in batch job completion and address them by optimizing or reviewing the logic in the process.