Holly tested this at https://bugfest-goldenrod.folio.ebsco.com/ using a fresh user (one that has never been used before in testing fees/fines) and discovered that this error cannot be reproduced. The test users she was using became corrupt from other bugs that have since been fixed.

, yes, it should work.

: If I pick a user on https://bugfest-goldenrod.folio.ebsco.com/ that has never had fees/fines and test this on him/her, it should work? I will try this now.

, Tested on Bugfest. Changing the patron group does make the block appear/disappear as long as new or "clean" (without previously created fees/fines) user is used. Failure to do the same for users with old fees/fines is to be expected. Here is why:

• Every time a fee/fine is created/updated/closed, a corresponding event is fired. At mod-patron-blocks we collect those events and use their payload to create and maintain a "user profile" of sorts. This profile tells us what fees/fines a patron owns, and this is the information we use to calculate automated blocks for the patron.

• We can't just call mod-feesfines directly and see what fees/fines the patron owns, due to limitations of FOLIO platform.

• Reliability of this approach depends completely on synchronicity of data between mod-feesfines and mod-patron-blocks.

• This approach will fail if you use a patron who owns fees/fines which were created before we started collecting events.

This is the case with the patron you used for testing: their "profile" currently is out of sync with data stored in mod-feesfines. It's the same issue with corrupt data that can't be cleared that we see in . The block was created, but not cleared properly due to a bug that was fixed at a later date. We'll continue to see these so it's best to test patron blocks with new users instead of blocks previously created. We could also consider a new feature that allows a user to clear them.