Comment 1 for bug 1726918

I'm unable to replicate this on current master, but I'm not seeing any commits in the history for the two obvious files to check(staff/circ/patron/app.js and staff/services/patron_search.js) that would have resolved it. Is it possible that hatch session storage key eg.circ.last_alerted_patron was set to the specific test patron when encountering the issue?