Bug 23541 - Duplicate Hold Notifications
Summary: Duplicate Hold Notifications
Status: CLOSED WORKSFORME
Alias: None
Product: Koha
Classification: Unclassified
Component: Notices (show other bugs)
Version: 18.11
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-05 12:15 UTC by Kelly McElligott
Modified: 2023-06-08 22:26 UTC (History)
10 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kelly McElligott 2019-09-05 12:15:50 UTC
In 18.11, it was reported that library patrons from several libraries were receiving duplicate hold notifications. This is not performing consistently, and hard to reproduce.  Both Firefox and Chrome browsers have performed the same way.  It would appear that the hold request has been sent twice and unfortunately, it can't be determined what is causing this.  The patrons that have received duplicate hold notifications don't consistently get the duplicate hold notification, it is quite random.  This duplicate hold notifications are occurring in Email form and a variety of email providers are doing this. These duplicate hold notifications are happening on holds on the shelf and checked in holds, this is happening sporadically during the day.  The libraries that have reported this are not using SIP devices and only one is using a RFID scanner.
Comment 1 Benjamin Daeuber 2019-09-05 13:30:30 UTC
This is creating two entries in the notification table, so this isn't an issue on the email server end, it's definitely in Koha.
Comment 2 AspenCat Team 2019-10-28 20:30:34 UTC
One of our libraries reported this happening again.  We've seen this a number of times now.
Comment 3 Lucy Vaux-Harvey 2019-10-29 12:23:46 UTC
We are seeing this exactly as Kelly describes with a library at 18.11.04.
Comment 4 Nick Clemens 2022-06-10 12:43:10 UTC
Still valid?
Comment 5 Lucy Vaux-Harvey 2022-06-10 13:15:15 UTC
Thanks for the reminder Nick - I haven't received any further reports of this issue.