Skip to main content
Solved

FME Flow 'Debug' Log Option for Workspaces in Automations

  • September 16, 2024
  • 4 replies
  • 135 views
mmccart
Enthusiast
Forum|alt.badge.img+27

In the ‘Run Workspace Dialog, there is a ‘Log Debug’ option under ‘Advanced’ settings here:

 

 

Why isn’t there an option to enable this ‘Log Debug’ in Automations when configuring the ‘Action>Run Workspace’ interface? I need debug logging details to run my automation in ‘production’ mode. It’s not honoring the logging setting when I published from FME Form. Shouldn’t the option be here: 

 

My ultimate goal is to have log files from workspaces ran within Automation have full debug logging enabled.

Is there some setting in a config file I can change?

Version: FME Form/Flow 2024.1.1.0 (Build 24619)

Best answer by mark2atsafe

Hi Mark,

It looks like "log debug” couldn’t be added to Automations because of another requirement blocking it. So there won’t be any way to get debug logging at the present time.

Although I certainly can’t guarantee anything, the good news is that the requirement is marked as a high priority and scheduled for 2025. So I am hopeful of an update soon.

If you do need to follow up directly with support at any point, the issue number to quote to them is FMEFLOW-23278.

Mark

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

mmccart
Enthusiast
Forum|alt.badge.img+27
  • mmccartEnthusiast
  • Author
  • Enthusiast
  • 81 replies
  • September 19, 2024

Update/Additional information:

I went into the following messagelogger.properties files and changed the ‘DEBUG_LEVEL’ from ‘NONE’ to all the other options (i.e. LOW, MEDIUM, HIGH, SUPER_VERBOSE) and no change to log file for workspaces ran via an Automation. 

Paths for files:

  1. ...\Server\config\logger\core
  2. ...\Server\config\logger\engine
  3. ...\Utilities\config

We have a distributed Engine and I changed the messagelogger.properties file on that machine as well.

Are there any other config files that I might be missing to enable DEBUG_LEVEL logging on all workspaces ran via Automations? 

mark2atsafe
Safer
Forum|alt.badge.img+56
  • mark2atsafeSafer
  • Safer
  • 2554 replies
  • Best Answer
  • September 19, 2024

Hi Mark,

It looks like "log debug” couldn’t be added to Automations because of another requirement blocking it. So there won’t be any way to get debug logging at the present time.

Although I certainly can’t guarantee anything, the good news is that the requirement is marked as a high priority and scheduled for 2025. So I am hopeful of an update soon.

If you do need to follow up directly with support at any point, the issue number to quote to them is FMEFLOW-23278.

Mark

FME Evangelist to the Rich and Famous!!
mmccart
Enthusiast
Forum|alt.badge.img+27
  • mmccartEnthusiast
  • Author
  • Enthusiast
  • 81 replies
  • September 30, 2024

Thanks @mark2atsafe for the update. Will work on a plan B.

ebygomm
Influencer
Forum|alt.badge.img+44
  • ebygommInfluencer
  • Influencer
  • 3427 replies
  • November 6, 2024

I have workspaces running within automations in Flow 2024.1 that do have debug logging enabled, but they’ve been migrated as is from an earlier version. 

 

If triggered directly, these workspaces also run in debug mode even if the radio button under advanced settings is set to off. 

 

I’ve been able to identify them by reading the .fmw files as text and looking for this line

 

Community Stats

32,068
Posts
121,762
Replies
39,693
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.