{"id":"6af8d8018e5f798c1c418aa2","title":"2026 11 14 Issue 231","path":"how-to/committee/release-notes/2026-11-14-issue-231","contentMarkdown":"# 14-Nov-2026 — back up S3 for sites whose bucket is in another AWS account, show clearly what Start [#231](https://github.com/Ramblers-GB/ngx-ramblers/issues/231)\n\n## [build 1084](https://github.com/Ramblers-GB/ngx-ramblers/actions/runs/43643673666) — [commit 44e851e](https://github.com/Ramblers-GB/ngx-ramblers/commit/44e851e37b486d7b375be6ba96fd4c60c2730c3b)\n\n_____\n\n## What's new\n\n- Scheduled and manual S3 backups now work for sites on the new London buckets. Previously every run for those sites showed `Failed` with `0 copied, 0 skipped, Access Denied` in the S3 Objects column on Backup and Restore → History, because the backup tried to read their bucket with a key from a different AWS account.\n- When a site's bucket belongs to a different AWS account from the backup bucket, the backup reads the site's files with that site's own key and copies each one into the backup bucket. The session log says when this happens.\n- Restoring S3 into such a site works the same way in reverse, writing with the site's own key.\n- Sites whose bucket shares an account with the backup bucket are unchanged.\n- On Backup and Restore, the environments in the address bar now set the environment picker on every tab, not just History. Open a link such as `?tab=backup&environments=group-one,group-two` and the Backup tab has those environments ready to back up.\n- Changing environments on the Backup or History tab updates the address bar, and switching tabs keeps the same environments, so a link copied from any tab opens with the same choice.\n- When exactly one environment is chosen, the Restore tab's Target Environment is set to it. Picking a Target Environment on the Restore tab makes it the chosen environment everywhere. With several environments chosen, the Restore target is left for you to pick.\n- Start Backup now shows one message at the top of the page saying which environments were queued and which were not (with the reason), and that History is showing only those environments.\n- After Start Backup or Start Restore, History clears its Triggered by and Status filters, so new sessions can no longer be hidden by a filter left over from earlier, such as Scheduled task and Completed.\n- Messages on Backup and Restore are now shown at all; before, start and error messages on this page never appeared.\n- Starting a backup for an environment that already has one queued or running is refused with a message such as \"A backup for group-one is already queued\", so a second click no longer piles up duplicate backups.\n- To cancel a queued session, open History, click its Abort button and confirm with the tick. The session will never start. Open the row to see who aborted it.\n- Sessions now record the name of the administrator who started or aborted them instead of \"unknown\".\n- History keeps updating live after the site restarts or the connection drops. Before, a restart (for example a deploy) left the page showing sessions as Pending or In Progress long after they had finished.","contentHtml":"<h1>14-Nov-2026 — back up S3 for sites whose bucket is in another AWS account, show clearly what Start <a href=\"https://github.com/Ramblers-GB/ngx-ramblers/issues/231\">#231</a></h1>\n<h2><a href=\"https://github.com/Ramblers-GB/ngx-ramblers/actions/runs/43643673666\">build 1084</a> — <a href=\"https://github.com/Ramblers-GB/ngx-ramblers/commit/44e851e37b486d7b375be6ba96fd4c60c2730c3b\">commit 44e851e</a></h2>\n<hr>\n<h2>What&#39;s new</h2>\n<ul>\n<li>Scheduled and manual S3 backups now work for sites on the new London buckets. Previously every run for those sites showed <code>Failed</code> with <code>0 copied, 0 skipped, Access Denied</code> in the S3 Objects column on Backup and Restore → History, because the backup tried to read their bucket with a key from a different AWS account.</li>\n<li>When a site&#39;s bucket belongs to a different AWS account from the backup bucket, the backup reads the site&#39;s files with that site&#39;s own key and copies each one into the backup bucket. The session log says when this happens.</li>\n<li>Restoring S3 into such a site works the same way in reverse, writing with the site&#39;s own key.</li>\n<li>Sites whose bucket shares an account with the backup bucket are unchanged.</li>\n<li>On Backup and Restore, the environments in the address bar now set the environment picker on every tab, not just History. Open a link such as <code>?tab=backup&amp;environments=group-one,group-two</code> and the Backup tab has those environments ready to back up.</li>\n<li>Changing environments on the Backup or History tab updates the address bar, and switching tabs keeps the same environments, so a link copied from any tab opens with the same choice.</li>\n<li>When exactly one environment is chosen, the Restore tab&#39;s Target Environment is set to it. Picking a Target Environment on the Restore tab makes it the chosen environment everywhere. With several environments chosen, the Restore target is left for you to pick.</li>\n<li>Start Backup now shows one message at the top of the page saying which environments were queued and which were not (with the reason), and that History is showing only those environments.</li>\n<li>After Start Backup or Start Restore, History clears its Triggered by and Status filters, so new sessions can no longer be hidden by a filter left over from earlier, such as Scheduled task and Completed.</li>\n<li>Messages on Backup and Restore are now shown at all; before, start and error messages on this page never appeared.</li>\n<li>Starting a backup for an environment that already has one queued or running is refused with a message such as &quot;A backup for group-one is already queued&quot;, so a second click no longer piles up duplicate backups.</li>\n<li>To cancel a queued session, open History, click its Abort button and confirm with the tick. The session will never start. Open the row to see who aborted it.</li>\n<li>Sessions now record the name of the administrator who started or aborted them instead of &quot;unknown&quot;.</li>\n<li>History keeps updating live after the site restarts or the connection drops. Before, a restart (for example a deploy) left the page showing sessions as Pending or In Progress long after they had finished.</li>\n</ul>\n"}