# 17-Nov-2026 — let the nightly backup finish again and keep manual backups running when nobody is [#445](https://github.com/Ramblers-GB/ngx-ramblers/issues/445)

## [build 1099](https://github.com/Ramblers-GB/ngx-ramblers/actions/runs/44192316959) — [commit ddaf90f](https://github.com/Ramblers-GB/ngx-ramblers/commit/ddaf90fee3b19bc7b5ee337a0ac03293c0b593b5)

_____

## What's new

- The nightly all-environments backup finishes in its usual time again. Since aborting a running backup was added, it had been taking many hours and was stopped at the four-hour limit, so the backups of 16 and 17 November failed.
- Aborting a running backup still works; it is noticed within about five seconds.
- A backup started from the Backup tab no longer stops part-way when nobody is watching. Fly was suspending the integration worker as idle once the page stopped polling it; the worker now keeps itself running for as long as any backup job is in progress, however it was started.
- Each run in Backup and Restore History has an abort button in its header while any of its sessions are pending or in progress. It is the same small button and confirm step as aborting a single session, with its own tooltip. Pending sessions are aborted before the running one, so the worker does not start the next environment part-way through.
- A scheduled task that is still running when a deploy or planned restart stops the server is now recorded in its history as failed with "Stopped by a deploy or planned restart before it finished", instead of being left as running and later reported as a vague failure.
- When Fly has no current memory reading for an app, System Settings diagnostics now says whether the machine is suspended or stopped, instead of suggesting it may have just restarted.
- In Backup and Restore History, the Environments filter takes the full width once more than three environments are selected, with Triggered by and Status on their own row underneath, so the selected environments no longer wrap into a narrow column.