Hello,

I have experienced unexplainable behaviour in an automation in FME Flow 2023 that had originally been created in FME Server 2021 after making some modifications.

Problem:
One of the workspace output paths has always contained a <space> and always has been wrapped in double quotes. With recent modifications (see context), the automation suddenly began splitting the output path on the space and treating it as a relative path - outputting to ./repositories/<right half of path>.

In addition to this, published parameters were no longer automatically refreshing on republishing of the workbench.

Context:
As mentioned, the automation had originally been created in v2021 and since the upgrade had been provided with the upgraded 2023 versions of the workbenches - which has been running smoothly. Recently, I’d made some large changes to the automation and the workbenches - renaming everything, adding additional workbench outputs, and streamlining the whole process. The key actions (I believe) were that I utilised the existing automation and updated the workspace nodes to point to the new versions.

I wasn’t able to spot any difference between the local versions and the published versions. The output file path was the same, still wrapped in quotes. The workbench worked when run manually, local and server side. It ran correctly when triggered with workspace runner individually. I tried restarting the Flow services.

Resolution & Questions:
I did resolve it in the end by removing the existing action node and replacing it, but I wanted to be sure it wouldn’t happen again, so I recreated the automation from new. I was hoping someone might shed some light on what may have occurred here as I’m not sure what actually went wrong.

• Do automations / nodes have versioning that aren’t automatically updated between Flow version changes?
• Is there some automation cache behind the scenes?
• In this case, should we always be creating new automations & nodes instead of repurposing them?

Thanks all!