Comment 5 for bug 1944986

I used the script recently for some post-COVID work and had an unexpected side effect.

Some standing penalties can be generated by the system (e.g. PATRON_EXCEEDS_COLLECTIONS_WARNING) based on a threshold, but can also be manually archived by staff even when the conditions that resulted in the penalty still exist.

If the patron interacts with the system in a way that causes penalties to be regenerated OR a batch script runs that updates everyone's penalties, the manually archived penalty can be re-applied for patrons that still meet the required conditions.

If the penalty in question causes, say, a billing notice to be sent, regenerating such penalties can cause a large pile of notices to be sent to patrons that have already received the same notice. Good times.

Removing pullrequest. Adding Needs discussion.