Skip to main content

Hi, 

every day I monitor hundreds of jobs on an instance of FME Flow. Whenever an error occurs, I look in the log file of that job to figure out what went wrong. Now the problem is that sometimes that log file is empty, or only consists of a few warnings. I found out that it is related to which log-filters was configured when the workspace was uploaded to FME Flow. 

Is there any way to change the global log-filters on FME Flow, to make sure every workspace uses the same filter?

 

Best regards,

Jacques

What version of Flow are you using?

 

Log settings are no longer embedded in the workspaces (from 2024 onwards I think). But workspaces that have embedded settings still use these if they’ve been migrated from an earlier instance of Flow, and changing the settings on Flow does not override this.

e.g. If a workspace was uploaded with debug logging enabled, it still runs with debug logging even if debug logging is turned off on Flow under the advanced parameters


What version of Flow are you using?

We are running in 2023.1.2. 

 

Log settings are no longer embedded in the workspaces (from 2024 onwards I think). But workspaces that have embedded settings still use these if they’ve been migrated from an earlier instance of Flow, and changing the settings on Flow does not override this.

Okay, this was great information. We are about to upgrade to 2025 later this year which might solve my problems then. 


If you just migrate your workspaces, then the debug logging will still be embedded. You would have to reupload from Form to remove that I think.

 

But going forward, new workspaces uploaded to flow won’t have these set.


@ebygomm 

Thanks!