Skip to main content
Solved

Workspace runner after a feature writer fails to start

  • May 5, 2022
  • 5 replies
  • 124 views
T
Forum|alt.badge.img

Hi,

I'm trying to start a workspace runner just after a FeatureWriter has finished running, but I am getting a weird error with a '@Tcl2 function':

 

...
WorkspaceRunner_ExecutorAndRouter (TestFactory): An error was encountered evaluating a TestFactory test: An error occurred while evaluating a test parameter: @Tcl2 function requires exactly one argument -- the expression to evaluate.  If you are using static function evaluation, only one $[ .. ] pair can be on a single logical mapping file line due to parser limitations
FeatureWriter_6_SUMMARY_-1_836_Player (RecorderFactory): An error was encountered evaluating a TestFactory test: An error occurred while evaluating a test parameter: @Tcl2 function requires exactly one argument -- the expression to evaluate.  If you are using static function evaluation, only one $[ .. ] pair can be on a single logical mapping file line due to parser limitations
...

This is happening with different workbenches. It is fine if I copy the whole workbench... But it's a large one and I'd rather not to

 

I tried a sampler to only get one feature, but not luck. 

 

any ideas how to be able to launch a workspace runner from a FeatureWriter? 

 

Best answer by redgeographics

Could the problem be from the WorkspaceRunner itself?

It shows parameters as 'not set', but they actually are:

image

That's definitely odd and I agree, it looks like there might be something going on with the WorkspaceRunner. The TCL error message isn't extremely helpful though, and what with TCL being the deeper level scripting language that part of FME is built upon I'm guessing there's something fundamentally fishy.

 

Could it be that there's a space in any of those parameters you've set on the WorkspaceRunner? Or maybe double double quotes? That might make a TCL function inside that workspace think there's a wrong number of parameters being passed.

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.

5 replies

redgeographics
Celebrity
Forum|alt.badge.img+59
  • redgeographicsCelebrity
  • Celebrity
  • 3699 replies
  • May 5, 2022

The FeatureWriter should output a summary feature, but I'm not sure if it does so when it fails.

 

One thing you could try is use a NoFeaturesTester (custom transformer from the FME hub) to trigger the WorkspaceRunner regardless.

FME rocks! \m/
T
Forum|alt.badge.img
  • ts_84
  • Author
  • 21 replies
  • May 6, 2022

The FeatureWriter should output a summary feature, but I'm not sure if it does so when it fails.

 

One thing you could try is use a NoFeaturesTester (custom transformer from the FME hub) to trigger the WorkspaceRunner regardless.

Thanks for the suggestion. The FeatureWriters do output a summary in this case though and files are created. I really wonder why the workbench runner is not happy

image

T
Forum|alt.badge.img
  • ts_84
  • Author
  • 21 replies
  • May 6, 2022

The FeatureWriter should output a summary feature, but I'm not sure if it does so when it fails.

 

One thing you could try is use a NoFeaturesTester (custom transformer from the FME hub) to trigger the WorkspaceRunner regardless.

Could the problem be from the WorkspaceRunner itself?

It shows parameters as 'not set', but they actually are:

image

redgeographics
Celebrity
Forum|alt.badge.img+59
  • redgeographicsCelebrity
  • Celebrity
  • 3699 replies
  • Best Answer
  • May 6, 2022

Could the problem be from the WorkspaceRunner itself?

It shows parameters as 'not set', but they actually are:

image

That's definitely odd and I agree, it looks like there might be something going on with the WorkspaceRunner. The TCL error message isn't extremely helpful though, and what with TCL being the deeper level scripting language that part of FME is built upon I'm guessing there's something fundamentally fishy.

 

Could it be that there's a space in any of those parameters you've set on the WorkspaceRunner? Or maybe double double quotes? That might make a TCL function inside that workspace think there's a wrong number of parameters being passed.

FME rocks! \m/
T
Forum|alt.badge.img
  • ts_84
  • Author
  • 21 replies
  • May 9, 2022

Could the problem be from the WorkspaceRunner itself?

It shows parameters as 'not set', but they actually are:

image

That's exactly what the problem was. Spaces. Thank you! I was using a One Drive location on my local and this had spaces in the filepath of the workspace, hence why it was confused with multiple arguments...

This might not be an easy fix for FME but it would be good if it was communicated to the end user.

Community Stats

32,066
Posts
121,745
Replies
39,692
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.