Have you tried setting "Wait for job to complete" to Yes?
You will proably also want to read through the WorkspaceRunner documentation, there are several useful tips there:
http://docs.safe.com/fme/2018.1/html/FME_Desktop_Documentation/FME_Transformers/Transformers/workspacerunner.htm
Have you tried setting "Wait for job to complete" to Yes?
You will proably also want to read through the WorkspaceRunner documentation, there are several useful tips there:
http://docs.safe.com/fme/2018.1/html/FME_Desktop_Documentation/FME_Transformers/Transformers/workspacerunner.htm
This, and use a different WorkspaceRunner for each Workspace.
Master:
Slave a:
01_master.fmwt
Sorry, I was unclear. First, having to run a series of runners kind of defy the purpose, I think.
So I read the current list of workspaces from a folder and feed them to the runner like this.
The documentation speaks only of the workspace in singular, and the WorkSpaceRunner only allows input of one workspace, so I came up with the list idea above. And I have of course set the switch to wait for the job to complete. But which job? Will it stop on the first unsuccessful one, or will it simply report a failure and go on with the next? I am reluctant to make it fail on purpose.
Going over the above, I now realised a mistake. I used path_filename instead of path_windows for the parameter to pass on to the runner. This caused all workspaces to fail.
Running the above set up seems to work now. Yipee!
It's a pity though that I get no feedback from each process, neither during the run nor afterwards, other than that it went well.
/Mats.E