https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24203 --- Comment #7 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- Hi y'all. The long overdue cronjob and the overdue notice system are two fundamentally disconnected things in Koha. However, it's been standard practice with ByWater partners to use the third overdue notice to alert patrons to the replacement charge generated by the long overdue cron. That already presented some issues based on holidays. As Christopher points out, Bug 20436 moves the potential behavior of the long overdue cron further away from the rather inflexible behavior of the overdue notices. If we want to maintain our practice of using the third overdue notice to alert patrons to the charges generated by the long overdue cronjob, then we need to do some work to make the two processes able to line up better. That would mean teaching the overdues to differ by item type and also teaching the long overdue cron to skip holidays (again, bug 18064. However, the new patron_emailer cron cron could be used to send a notice about items impacted by the long overdue cron without involving the overdues process at all. I'd suggest that approach at least as a short term answer (if not as an alternative to this bug entirely). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.