Can anyone explain how and when new Pledged Opportunities are created, and how the Next Donation Date Match Range is used in the creation of new pledged opportunities? And, does anyone know why Salesforce recommends that setting be 3 as the default and nothing higher than 20? I was under the impression that with Enhanced Recurring Donations, only one Pledged Opportunity can exist at a time, and when that one is closed the next one is generated. Depending on the Next Donation Date Match Range, it's either created in the current month, or the next month. Two things are happening in my org that I don't understand:
1) Multiple pledged opportunities exist and it's clear that batch processing creates a new one as soon as the current one is a day past its close date. I thought the only way a new pledged opp is created is when the current one is closed.
2) On 2/28 we closed our pledged donations with close dates between 1/24 and 2/23 (in small batches of 30-40). When we did this, we got error messages for each batch we ran (see below). For almost all of these, the next pledged donation that was created skipped a month. Our Next Donation Date Match Range was set to 28 at the time. I changed that to 27 and during overnight batch processing it created the pledged donations it had skipped for anything with a close date (day of the month) greater or equal to the day I did this (a few days ago). For the ones with days prior to the day I did this, I had to manually create the missing pledged donations. I cannot recreate what happened because it's not possible to back-date recurring donations. I've been doing every kind of test I can think of by changing the Next Donation Date Match Range, but cannot make it skip a month. I need to understand if there's something in my settings that caused this, or if there is a bug of some sort.
The error message we received when closing this batch of donations: Error #1:
Error Type: Job Error
Error Date: 2023-02-28 23:39:56
Message: "There were one more errors updating or inserting the following records:
* 0011R000026HN8IQAW: UNABLE_TO_LOCK_ROW- unable to obtain exclusive access to this record or 33 records:
Context: CRLP.AccountHardCredit
Stack Trace:
