{"id":"6a5891368e725357cf92fde8","title":"2026 07 16 Issue 310","path":"how-to/committee/release-notes/2026-07-16-issue-310","contentMarkdown":"# 16-Jul-2026 — the inbox opens quickly again [ref #310](https://github.com/nbarrett/ngx-ramblers/issues/310)\n\n## [build 779](https://github.com/nbarrett/ngx-ramblers/actions/runs/29481355998) — [commit 6ec9409](https://github.com/nbarrett/ngx-ramblers/commit/6ec9409185965527074ab3a52dbe7637d26d422a)\n\n_____\n\n## What's new\n\nThe inbox had become slow to use. Opening it, listing message threads and checking which mailboxes your roles could see each took several seconds every time. That is now fixed, and the inbox responds straight away.\n\n## At a glance\n\n- Opening the inbox, listing threads and checking role mailboxes now respond almost instantly, rather than taking between 8 and 17 seconds each\n- Nothing has changed about how the inbox works, or what it shows you — only how quickly it comes back\n- The cause was the inbox loading the group's area map boundaries every single time it checked who was allowed to see a message, even though it never needed them. It now leaves that data well alone","contentHtml":"<h1>16-Jul-2026 — the inbox opens quickly again <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/310\">ref #310</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/29481355998\">build 779</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/6ec9409185965527074ab3a52dbe7637d26d422a\">commit 6ec9409</a></h2>\n<hr>\n<h2>What&#39;s new</h2>\n<p>The inbox had become slow to use. Opening it, listing message threads and checking which mailboxes your roles could see each took several seconds every time. That is now fixed, and the inbox responds straight away.</p>\n<h2>At a glance</h2>\n<ul>\n<li>Opening the inbox, listing threads and checking role mailboxes now respond almost instantly, rather than taking between 8 and 17 seconds each</li>\n<li>Nothing has changed about how the inbox works, or what it shows you — only how quickly it comes back</li>\n<li>The cause was the inbox loading the group&#39;s area map boundaries every single time it checked who was allowed to see a message, even though it never needed them. It now leaves that data well alone</li>\n</ul>\n"}