, and - It's true that real time notices cannot have multiple items and it was built this way. However, it would be preferable that the #loans tag for multiple items to "break" gracefully by rendering the single loan/item as it loops through the potential multiples. In it's purest form, real time is essentially in opposition with multiple items. For example, if it's a real time check in receipt notice, then every scan would generate a notice. Same would hold true for courtesy or overdue (typically used for minutely or hourly short term loans). I think a change to the UI would help. Instead of a checkbox for real time, it might help to offer a radio button (single option) for either real time (no bundling of multiples) or batch processed overnight (with bundling of multiples).

Update:
When exploring at the scheduled-notice-storage API, I discovered that Courtesy and Overdue notice records created before we unchecked "Real time" for our Courtesy and Overdue notice policies still had "sendInRealTime": true.

verified that the #loans tag does not work with real time notices. Since our Overdue and Courtesy notice all employ the #loan tag, this seemed a likely
culprit for why notices for older loans have recently been sent out without title information (ie the data contained within the loans tag).

We tested the hypothesis by changing "sendInRealTime": true to "sendInRealTime": false in all the notice records associated with one of our migrated loans. Having verified that the notices sent out after this update looked correct, we updated "sendInRealTime": true to "sendInRealTime": false in all our existing due date-triggered notice records.

We are hopeful that this will have solved remaining issues, but and I will need to double-check next week that this is the case.

Should the Description of this be fleshed out a bit to describe what the remaining issues are? And isn't this a bug rather than a story?

My impression of the state of things is that since our overdue and courtesy notices have (it seems) now been correctly set up to work with the newly implemented ability to schedule batch sending of notices, and to display several items in one notice, notices for newly created loans should be sent out and display tokens correctly.

However, we still do not have an explanation for - even less a way of preventing - notices for older loans (our current hypothesis is that this affects notices for loans checked out before the updates to notices functionality were implemented and we updated our settings to match those) being sent out without title information. We have so far ruled out issues with the templates we are currently using.

For the issue to be resolved, we need to understand why incorrect notices are being generated, and the extent of the issue (ie how many loans will be affected), so that, with that knowledge, we can take appropriate actions to either a) prevent incomplete notices from being sent out or b) inform our patrons.