Skip to main content
Solved

Top level resource folder not working in FME flow

  • November 3, 2025
  • 1 reply
  • 59 views

jonathan_vru
Contributor
Forum|alt.badge.img+7

 

I am trying to make a custom top level resource folder work, but i can't write the output of my apps and workspaces to the folder. 

 

If i try to write output to the custom folder, it fails almost immediately, and when i inspect the logfile it just says 

  • Log Error
  • The log file for job ID "816" does not exist.

Did i forget some steps in the configuration of the custom folder? Or what did i do wrong?

 

Thanks in advance for the help!

 

 

For reference what i did:

Adding Top-level resource folder in FME Flow | Community

Best answer by zoe.forbes

Hi Jonathan,

Creating a top-level folder in Resources via fmeflowconfig.txt causes the folder to appear in the UI, but does not create a macro. This means $(FME_SHAREDRESOURCE_MOI) will not be recognised by Flow when the workspace is run (assuming this is the SHAREDRESOURCE_NAME value you set, from ​@frro’s answer).

To mimic the expected behaviour from macros referencing top-level Resources, you can create a Deployment Parameter with name FME_SHAREDRESOURCE_MOI and value “C:\ProgramData\Safe Software\FMEFlow\resources\moi” or wherever the new moi folder is located. This allows $(FME_SHAREDRESOURCE_MOI) to be recognized in User Parameters or within Workspaces.

Please let me know if you have any questions about this!

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.

1 reply

zoe.forbes
Safer
Forum|alt.badge.img+5
  • Safer
  • Best Answer
  • November 6, 2025

Hi Jonathan,

Creating a top-level folder in Resources via fmeflowconfig.txt causes the folder to appear in the UI, but does not create a macro. This means $(FME_SHAREDRESOURCE_MOI) will not be recognised by Flow when the workspace is run (assuming this is the SHAREDRESOURCE_NAME value you set, from ​@frro’s answer).

To mimic the expected behaviour from macros referencing top-level Resources, you can create a Deployment Parameter with name FME_SHAREDRESOURCE_MOI and value “C:\ProgramData\Safe Software\FMEFlow\resources\moi” or wherever the new moi folder is located. This allows $(FME_SHAREDRESOURCE_MOI) to be recognized in User Parameters or within Workspaces.

Please let me know if you have any questions about this!