I would suggest: If you run using batch deploy or using FME Server, turn off feature caching automatically.

Executing a partial run is not an option when using batch or FME Server anyway.

Or/And make the bool accessible from FME_MacroValues if featureCaching is enabled/true or disabled/false.

If turning Feature Caching on in one workspace that I currently developing did not affect any other workspace I have open or choose to open subsequently, that would be great. Often I'm running completed workspaces that need to run as fast as possible, to serve others, while continuing to develop another separate workspace.

Extra issue when I work with 2 workspaces simultaneously. One of them I need to have feature caching on, the other one needs to have featurecaching off (testing parallell processing). They take some time to run so thats why I need to work on the smaller project the same time as the large one. Now I always have to remember to switch on/off featurecaching on the other workspace after I have started to run it.

Yeah, I pretty much stated the same problem: https://knowledge.safe.com/content/idea/68833/new-workspace-parameter-always-disable-featurecach.html

All run options should be associated with an individual workspace (local) and not impact the run of other workspaces (global). Especially if it results in a destructive operation.

This does happen.

RT @daleatsafe: yes, it does happen, but if you switch off caching in one Workbench instance, it gets switched off for all instances. It would be good if the toggle would only apply to the instance it's clicked in.

I started to create this exact request Jan 2022, but found this one languishing since 2018. This would be super useful and save a bunch of time when we realize that caching is on, have to stop the job, and start the run over again. Or, vice versa.