Hi Beth,

This could have something to do with how your notice action triggers are
configured, but I can think of a couple of bugs that might be related:

https://bugs.launchpad.net/evergreen/+bug/1758975 - Item status can be set
to Lost and Paid inappropriately when closing a transaction for a Long
Overdue or Lost returned item

If the above bug were the cause, you would not see a payment for the lost
billing when viewing the full details of the billing transaction.

https://bugs.launchpad.net/evergreen/+bug/1692116 - Action trigger
validators problems for Long Overdue items

We have seen the above bug with notices for Long Overdue items that were
paid, not sure if it also affects Lost items.

Hope this is helpful,

Michele M. Morgan, Technical Support Analyst
North of Boston Library Exchange, Danvers Massachusetts

On Mon, Mar 26, 2018 at 7:08 PM, Beth Longwell <blong...@eou.edu> wrote:

> Hi,
> A notice went out to one of our library's patrons yesterday indicating
> that their item was still overdue and had been marked lost even though it
> had gone to lost and paid back in January.
> We have the library setting enabled for lost and paid status and are on
> version 2.11.1
> Has anyone had this happen? Not sure where to look to fix.
> Thanks in advance,
> Beth Ross
> Sage Library System

Reply via email to