Updates and backup
Back up local data and results before replacing the portable program files.

Before you start
- Have the new release ZIP from the official download page.
- Have a private backup destination with enough space for app data and result files.
Steps
Locate both storage locations
In Cài đặt → Chung → Dữ liệu và an toàn, use Mở thư mục and record the actual data location. In Tạo tự động → Thư mục kết quả, use Mở and record the results location too.
These may be separate from the extracted program folder. Backing up only
FlowStudio.exedoes not back up profiles or outputs.Finish work and close before copying
Let active jobs finish and inspect any accepted jobs still needing attention before updating. Close the app and its managed Chrome processes before copying the data, so files are not changing during backup.
Copy the data directory and result directory to your private backup destination. Verify that the copies contain the expected files.
Replace the portable release
The verified public release does not auto-update. Check the release version and published SHA-256, then extract the complete ZIP into a writable program folder while the app is closed.
Launch
FlowStudio.exe. The branding change keeps this filename and the existing data folders; do not delete those folders as part of replacing program files.Verify before resuming a batch
Check Cài đặt → Giới thiệu, profile cards, Queue history, and Library files. Open the results folder and try one small job before resuming a batch.
Keep the backup until verification is complete. Treat profile backups as sensitive; Windows-protected secrets are machine-bound, so copying them is not a guaranteed migration to another PC.
When it worked
The new version opens with your expected profiles and result files, and a private backup is retained.
If something goes wrong
Does deleting the program remove all my data?
Not necessarily. Profiles and Library files can live outside the program directory. Identify their actual locations before removal.
Can I open an upgraded database in an older app?
Do not assume compatibility. The specification includes schema migrations and older-version rejection for newer databases. Keep a pre-update backup rather than relying on downgrading in place.
