JonGeorg,

I know this doesn't exactly answer your question, but we run a custom Perl
job daily at 1:00 am to check for failed and missed auto-renewals. This
process will fix failed auto-renewals and create the events for those that
it deems to have been missed.

We've had a lot of issues with auto-renewals because we run something like
13,000 per day on average, sometimes more than 30,000.

We also eliminated the 2-day courtesy notice by changing the wording of the
auto-renewal email notice so that it essentially serves both purposes.

We split our auto-renewals up to run at different times throughout the day
for different member libraries using filters. We run them every other hour
throughout the day now. This has revealed some interesting issues,
including a race condition with checkin that can occur.

Also, you don't want auto-renewals running at the same time as overdue and
setting items lost triggers, at least not on the same machine. I highly
recommend running these on different utility instances.

Jason

On Fri, Oct 10, 2025 at 4:35 PM JonGeorg SageLibrary via Evergreen-general <
[email protected]> wrote:

> We've had instances where autorenewals don't run in the morning
> automatically as they should. Is there an easy way that I can check every
> morning to ensure that it all ran correctly?
>
> Yes, I can do a grep against the syslog for auto_renewal=t which will show
> me instances of where it worked, but I'm hoping for something more
> mangeable than that- partially because I'm trying to figure out if it's
> limited to one library or all.
>
> Thanks
> -Jon
> _______________________________________________
> Evergreen-general mailing list -- [email protected]
> To unsubscribe send an email to
> [email protected]
>


-- 

Jason Stephenson (he/him)
ILS Manager, C/W MARS, Inc.

------------------------------

[image: icon] [email protected] | [image: icon]www.cwmars.org

[image: icon] 508-755-3323 x 418
_______________________________________________
Evergreen-general mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to