I’ve noticed a few issues since upgrading FME Form & Flow (FME Flow 2026.1 Build 26103 - win64) that seem to show up when I’m also developing in FME Form while remoted into our FME test VM.
This is how I usually work, mainly because some jobs take a while to run and if I do them locally my PC can go to sleep after 5 minutes and the jobs fail. This setup has never had an issue in the past.
Since the upgrade though, running Form this way can cause problems with FME Flow on the same VM. When I’m running heavier workbenches and CPU hits 100%, Flow can become unresponsive or look like it’s soft‑locked. This never happened before the upgrade.
One thing I’ve noticed is that this seems to mostly affect SSO sessions. My theory is that when CPU is maxed out, Flow struggles to grab required info for SSO before it expires. Just a guess.
I am also concerned that FME flow may soft lock itsself if it is running 100% cpu and the user cannot log in via SSO (yet to be tested)
It also feels like the newer version of FME Form uses more resources than it used to, which makes it easier to hit this situation when Form and Flow are sharing the same VM.
Has anyone else had issues with fme form/flow using more resources and that causing issues with flow responsiveness?
Thanks