Comment 2 for bug 1823225

Changing importance to High on this as it allows circulation transactions to proceed that should be blocked.

We have recently configured new patron blocks and have run across this issue.

Various processes in Evergreen will calculate penalties. Some examples are circulation transactions and fine generation. But retrieving a patron in the client or opac does not calculate penalties. This leads to the situation where a patron is allowed to perform a transaction that should be blocked. It also causes confusion for staff as one transaction is allowed, but subsequent transactions are blocked.

To reproduce this on a Concerto system:

Check out the following 2 items to patron 99999376864:

CONC40000628
CONC50000720

- In Items Out, select CONC50000720, and under Actions, choose Mark Lost
- Edit the stock penalty threshold for PATRON_EXCEEDS_LOST_COUNT, changing the stock threshold to 1
- Retrieve the patron and note there is no block even after refreshing.
- In Items Out, select CONC40000628, and under Actions, choose Renew
- Note that the renewal proceeds normally, but the patron now has the 'Patron exceeds max lost item threshold' block
- Select the other item and attempt to renew.

Note that the block now appropriately prevents renewal.