Skip to main content
  • EN

Dear All,

 

I am facing a very weird issue : I want to run another workspace using a workspacerunner with a set of user parameters. Sometimes it works, or sometimes I get a UNDEFINED MACRO error. What is really strange, it is that in some FME workspaces it works very well and the workspacerunner does the job - but in another workspace a workspacerunner (that calls exactly the same script with exactly the same set of input parameters) fails with the UNDEFINED MACRO failure. Even stranger : when I copy-paste the workspacerunner that does not work in the same workspace of the workspacerunners that works, it also does not work -> so in the same workspace I have 2 workspacerunners exactly identical, one working and the other raising a UNDEFINED macro error ???!!!

 

I've spent days trying to understand what was wrong in my script and/or parameter settings, but I end up thinking something else might be wrong... Do you have any ideas what could cause the issue ?

Particular cache files to delete ?

 

Are there some known bugs already reported related to that ? (I've read all the related questions of the forum I've found, but did not exactly find a one matching one).

 

Also running the script called in the WorkspaceRunner with a SystemCaller works perfectly, so I guess it is not my use of the parameters that cause the failure...

 

I am really desperate because I've spent sooooo much time on that that if any of you could help, it would a miracle !!!

 

Thanks in advance

 

 

 

 

Can you maybe share a sample workspace that replicates the issue you are having? Without it, it's a bit difficult to know for sure what's going on.

 

However, I recently encountered some issues with the WorkspaceRunner as well. How did you provide the values for the parameters at the WorkspaceRunner (i.e. for the 'sub-workspace' being run)? As 'direct values', or did you set them with an attribute value or a parameter value (of/in the main workspace).

If you configured them with a parameter, can you maybe check if the issue doesn't occur when you configure the WorkspaceRunner with 'direct values'?

 

I recently seemed to encounter some issues when passing along parameters values in nested Custom Transformers. See the following question I posted on the FME Community: https://community.safe.com/s/question/0D5Dm00000lTIOrKAO

Although that's related to (nested) Custom Transformers, I noticed the same kind of strange behaviour when I passed the parameter along trough a WorkspaceRunner.

 

Reply


Community Stats

30,112
Posts
114,305
Replies
37,745
Members
Terms & ConditionsCookie settings
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.