Summary: | Problem with holds when ExpireReservesMaxPickUpDelay is active | ||
---|---|---|---|
Product: | Koha | Reporter: | Patrick Robitaille <patrick.robitaille> |
Component: | Hold requests | Assignee: | Bugs List <koha-bugs> |
Status: | RESOLVED INVALID | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | gmcharlt, katrin.fischer, marjorie.barry-vila |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: |
Description
Patrick Robitaille
2019-04-11 20:07:29 UTC
Hi Patrick, is this bug still happening for you? Could you check the expirationdate of the waiting hold in the reserves table? This should be the date calculated for pickup from ExpireReservesMaxPickUpDelay and the day the hold is cancelld by the cronjob if not picked up. I believe this might have been due to how the cancel_expired_holds.pl had been set up. |