Skip to main content
New

FME Form/Workbench Connection Storage on FME Flow - caching for fault tolerance?

Related products:FME FormFME FlowIntegrations
  • November 20, 2025
  • 0 replies
  • 9 views

phoeffler
Contributor
Forum|alt.badge.img+7

I’m interested in using FME Flow for Connection Storage in FME Workbench.

We have a single FME Flow instance that does not have redundancy. I’m concerned that if Flow is unavailable, that FME Workbench will effectively also be rendered unusable if I use Flow for connection storage, based on what I’ve read in the documentation.

Further, FME Form provides me a sort of redundancy at the moment - if Flow is unavailable or if the engines are consumed, I can run my processes locally, as a last resort. In my understanding, moving my connections to Flow would remove this redundancy and leave me more vulnerable to network/infrastructure/system issues.

If the above is true, would it be possible to maintain a local cache of connections, similar to the default Personal Database Connection Storage, where it prompts for and perhaps even requires connection and syncing to Flow, but has some sort of fail-back mechanism in the event of failure?

I could keep an export of connections locally, or a Shared Database copy, but this will go stale and defeats the purpose of the FME Flow option, I imagine.

Thanks for any thoughts or corrections on the above.