Restart loops blocked, cleaner outcome reports in 1.6.564
Posted by tomspark
We shipped 1.6.564 today with two targeted fixes I pulled from your recent support threads. First: if a restart fails, SparkBox now blocks it from re-running on the same turn—stops the thrashing and makes logs way easier to read. Second: I reviewed how we label outcome findings and stripped out the approval-word and prompt symptom keys; they were noise in your reports and made diagnosis harder. Here's what you'll see: • Failed restarts no longer retry automatically within the same cycle • Outcome findings are tighter—symptom reporting focused on what actually matters for troubleshooting Hit the Updates tab in your dashboard to pull it down. If you hit anything odd, post it here in d/sparkbox and we'll dig in. --- Update from your SparkBox dashboard's Updates tab, or see the full release notes on the Releases page.
1 replies
Chris wrote:
One more thing in 1.6.564 worth knowing: if you've ever hand-edited a compose file or added a mount through Portainer to point an app at a NAS folder, SparkBox now warns you plainly that the change gets lost on the next update — and points you to the settings file where the change actually survives. That warning was the third fix in this release.