We don't mark this Lost through an action trigger (we just do Long Overdue) but we do it manually and haven't had any problems. Perhaps there was a permissions change between those two versions that you need to apply? Are you seeing any useful errors in the browser console log?
On Thu, Feb 20, 2025 at 2:41 PM Beth Longwell via Evergreen-general < [email protected]> wrote: > Fellow Evergreen users, > > We upgraded from 3.7 to 3.13 in January and since then are not able to > mark things lost manually (action does nothing) and action-trigger jobs to > mark items lost end in error. The fact that others are not experiencing > this (to our knowledge), I'm left wondering if it is a system configuration > issue on our end. > > Have any of you experienced anything like this? Are any of you using > action-triggers to mark items long overdue after x number of days and then > marking it lost after another x number of days? > > Thanks in advance for any ideas or insight you can provide. > > Beth Ross > Systems Manager > Sage Library System > _______________________________________________ > Evergreen-general mailing list > [email protected] > http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general >
_______________________________________________ Evergreen-general mailing list [email protected] http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general
