Preserve/Retrieve Notices When API Connection Fails
We recently upgraded to Sierra 6.4...
Something transpired where there were issues with the Sierra API as a result of the upgrade. Initially these issues manifested through the inability to login to our BiblioCommons discovery layer.
III support made some tweaks to the API services & it was eventually sorted, but we've since learned that because of this lost connection, notices generated & queued for sending in LX Starter that morning failed to send. So, on top of not being able to login to our primary discovery layer for most of the day following our upgrade, many of our users will soon find out they did not receive an expected notice re: their borrowing activity.
We would like to see a way, when this occurs, for notices to be preserved & resent, either manually or automatically.
Shawn P. Farrell
shared this idea
-
Shawn P. Farrell
commented
As Ray notes, this can happen again, as it did outside of our recent upgrade, only yesterday, with a batch of failed notices appearing at random. Not only did these (& those in the example in the original post) fail to send, there's no identifying data attached to the reporting.
-
Kathryn Brew
commented
We have had batches of emails "Failed to send" with no ability to re-send them. It is a critical issue for patrons and therefore for our libraries.
Automatic attempts to re-send would be the most helpful, along with a button for manual.
-
Ray Voelker
commented
This really should be considered a bug.
API endpoints can and do go down, so being able to deal with that should be core functionality
