Restore to FME Flow default without new installation

I second that.
It would be really useful to have the option to install FME Flow with no pre-installed workspaces, no inactive automations/schedules, no topics/publishers/subscribers, and no AR App. Just the bare minimum: the Admin user and the default roles (fmesuperuser/fmeadmin/fmeauthor/fmeuser).

All the other utilities and example content could instead be made available through FME Hub for download as Flow projects when needed.
On a related note, I also question the usefulness of the default “Temp” resource connection, since it isn’t required by the system and isn’t automatically cleaned up.


Edit : I’m realizing that this might be an idea close but not really corresponding to what you’re suggesting here. I’ll open another one

​@alexbiz :

The installation of FME Flow in version 2025.1.1 is smooth, and I'm quite happy with it — it's much easier now. After installation, you can test it using sample workspaces, which is a great feature. The only thing we missed was a 'clean-up' button to restore FME Flow to its default state without needing a full reinstallation.

It might be helpful to have a checkbox option during installation:

• [ ] Install without pre-loaded workspaces
• [ ] No inactive automations or schedules
• [ ] No topics, publishers, or subscribers
• [ ] No AR App

Do you mean, you want to install FME flow, do some testing, then wipe the slate clean or something else?

​@ebygomm upgrade/install FME flow → then backup & restore → it failed due to "javax.crypto.IllegalBlockSizeException: Data must not be longer than 245 bytes." 

it means restore was half done. As a workaround, i removed schedule, creating a new backup file without it, then restore again.  

Safe answer:

Unfortunately, you are correct that the only way to achieve this "factory reset" is to uninstall and reinstall FME Flow.  You could manually go about deleting all the automations, schedules, connections etc. but that would be a bit more time-consuming and may still result in some lingering files/resources.

If you haven't already, I would recommend adding this to our Product Ideas page, as this is where our development team gets a lot of their ideas from!

The backup and the dashboard schedules and workspaces may (optionally) remain