+4Is it possible to turn off log entries like these?
These just add clutter to the job reviewing process.
+5Hi
Thanks for the question!
Those log entries are helpful for the debugging process if you have any issues running jobs. That information may seem “too detailed”, but it’s very important to know the workspace version and potential memory issues. You are not able to remove them from the FME Flow job log files directly.
You could filter the job log using “warning”, “information” tags from the Flow UI, and it will only show the category you chose.
I hope it helps!
Cheers,
Skyler
+4I think your suggestion is reasonable in theory, but in practice it isn’t workable.
Based on the attached screenshot, it’s very difficult to quickly identify actual issues when the log is continually filled with these warnings.
The memory-related messages are particularly problematic, as I can’t add more physical memory to my instance without moving to a higher-cost tier.
I would recommend allowing users to disable logging for these types of messages. If that isn’t possible, they should at least be downgraded from warnings to informational messages. The details are interesting, but they aren’t actionable in a cloud environment.
| 3 | Workspace was last saved in FME version: FME 2025.1.3.1 (20251021 - Build 25645 - WIN64) |
| 23 | Failed to free sufficient memory to reach the process usage limit. To improve stability and performance please increase the memory available to FME. Available memory can be increased by adding physical RAM, increasing swap space, or closing other applications |
| 40 | FME Configuration: Extremely low initial memory conditions detected. To improve stability and performance please increase the memory available to FME. Available memory can be increased by adding physical RAM, increasing swap space, or closing other applications |
