Skip to main content
Question

FME Workbench 2022.2 automatically creates one output folder per input feature including extension when run from the command line

  • March 18, 2026
  • 1 reply
  • 27 views

jepen
Contributor
Forum|alt.badge.img+1

As the title suggests, I’m having an issue when running FME (2022.2) from the command line. I’m clipping several LAZ files with a polygon grid, and FME automatically puts the output files in one folder per LAZ file. I’m technically fine with this behavior as I was going to fan it out anyway, but the extension is included in the folder name (e.g. FILENAME_1.laz), which the following processing step in my pipeline cannot handle. 

 

The problem only occurs when run in the command line. Is there any setting anywhere so that I can get rid of the file extension in the folder names? 

1 reply

evieatsafe
Safer
  • Safer
  • March 19, 2026

Hi ​@jepen! Thanks for your question. 

That's a helpful detail that this issue only happens when running from the command line. I would expect the same outcome from running the workbench and from the command line. This could be a specific issue with how the command-line executor is handling the output naming.

To help us investigate further, could you share some additional details:

- The exact command you're using to run the workspace from the command line
- Your workspace (or at least a simplified version that reproduces the issue)
- Your FME build number (2022.2 has multiple updates - you can find this in Help > About FME Workbench)

This will help us narrow down whether there's a specific configuration or command-line parameter that's causing the extension to be included.

Curious about the reason for using command line and if there are workarounds in the meantime too. Have you tried running this through Task Scheduler or maybe see if a WorkspaceRunner has a different outcome? Let us know!