You now get a warning when an approved cross-session message is refused instead of delivered.
What's wrong with this entry?
If you approve a held message from another session but delivery is refused because cross-session messaging was turned off or set to refuse while the prompt was open, you now get an explicit warning that it was not delivered. Previously only a vanished message produced a notice.
That held message was NOT delivered: cross-session messaging was turned off (or set to refuse) while the prompt was open
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Messages injected by a host are classified separately from peer messages
Both mention cross
-
v2.1.234
Cross-session control requests check ids more carefully
Both mention cross
-
v2.1.234
Notice acks now wait for the record to persist
Both mention cross