Back to the changelog

• Improvement

  Updating no longer signs you out

  While services restart, for a few seconds the system cannot reach its own data. Previously this was indistinguishable from "your session is no longer valid", and the result was a sign-out. The two are now told apart: if the problem is temporary the page says so and retries, and you stay where you are. Instead of a shower of errors, a single bar appears at the top — "Connection to the server lost, retrying" — and disappears by itself as soon as things recover. Requests are retried for about twenty seconds, enough to cover a restart, while those that wouldn't improve by retrying are no longer retried pointlessly. And if you stay on the page while a new version is published, a discreet invitation to reload appears: no forced refresh, you choose when.

• Security

  No update starts without a verified backup

  The backup is taken before the update and then checked: if it fails, the update does not start at all. Better to postpone than to discover the problem afterwards. The check doesn't just confirm the file exists, but that it can actually be read. Backups rotate on their own and the destination folder can be chosen, so on a server it can match the one included in your provider's offsite copy. Restore drills are recorded with date and outcome: a backup never restored is only an assumption.

• Improvement

  Installing FlowSharp: a single path

  There was more than one way to install FlowSharp, and only one was maintained: the one described in the guide wasn't receiving the security updates applied to the other. It has been removed. A single, up-to-date path remains, and the documentation now describes an installation that actually works from start to finish. Sample credentials no longer appear in the guide — they hadn't been created for some time, yet were still listed as the way to sign in — and the first-run instructions have been corrected, as they pointed at a port not reachable from outside.

• Security

  Sample users on older installations

  Installations created before version 0.74.0 still contain the sample users, with passwords known to anyone who reads the source code. The block introduced in that version prevents them from being recreated, but doesn't remove those already there. There is now a documented procedure to check whether they exist and neutralise them safely, closing any sessions still open in their name at the same time. The procedure was carried out and verified before being published.

• Security

  Stricter checks on automations and attachments

  When you open an automation run, the system checks that it really belongs to the flow you started from. Previously the check only applied when every element to compare was present: if one was missing, the response went through anyway. A missing check no longer counts as a passed check. On attachments: when a procedure is deleted, the file can remain on disk because of a technical problem even though the procedure was removed correctly. Previously this ended up in a diagnostic line nobody reads; now it is recorded where it can be found, and there is a tool to locate and clean up files left behind.