# 04-Nov-2026 — keep collection cleanup from restarting the site [#424](https://github.com/nbarrett/ngx-ramblers/issues/424)

## [build 1060](https://github.com/nbarrett/ngx-ramblers/actions/runs/41803596210) — [commit 4fca9d1](https://github.com/nbarrett/ngx-ramblers/commit/4fca9d1127e5242c3cecb38671b9c068a6cbb524)

_____

## What's new

- Empty collection cleanup now removes collections one site at a time, using one database connection per site, so a large cleanup cannot exhaust memory and restart the website.
- The source environment used for site registration remains protected from cleanup, including when a submitted selection predates a source-setting change.
- If cleanup fails, the page titles the alert as a removal problem and shows the actual error from the server instead of a generic inspect message.
- On MongoDB Atlas Provisioning, the API keys warning stays hidden until Atlas settings have loaded, and Default cluster for new sites is a dropdown of known clusters rather than a free-text host.