RD2_OpportunityEvaluation_BATCH Runs Excessively Long Daily Despite Incremental Mode Enabled

In NPSP orgs using Enhanced Recurring Donations (RD2), the RD2_OpportunityEvaluation_BATCH job evaluates recurring donations and creates or updates related Opportunities. The batch can run for many hours each day (for example 10+ hours) over a very large population, and it may fail with:

Rate Limiting Exception: AsyncApexExecutions Limit exceeded

Two settings, not the incremental settings, are the usual drivers:

• "Exclude Closed Recurring Donations" is disabled, so Closed recurring donations (which never generate future installments) are pulled into the nightly evaluation population, inflating the record count.
• Recurring Donation Batch Size is set to 1, so the batch enqueues roughly one async Apex chunk per record instead of the default 50, consuming a large share of the org's 24-hour async Apex limit and driving the runtime up.

Important clarification: the "incremental" settings — Limit Recalculated Recurring Donations, RD Modified in Last Number of Days, and Incremental Last N Days Value Override — are Customizable Rollups (CRLP) settings that control the NPSP 06A/06B rollup batches. They do not govern the RD2 evaluation batch, so enabling them does not reduce the evaluation population.