Connection tracking for notify delivery
When tracking notifications often the same page is loaded immediately after submit. However, when opening multiple pages at once and then submitting an action the notification for that action can appear on the wrong page.
This happens because the notifications are tracked on the session level rather than the connection level. Notifications need to be assigned a connection-id and then that connection-id needs to be checked when draining the notification queue.
Since these informational messages are desired, the end user only notices minor confusion with this bug and it is a low priority.