Skip to main content
Archived

WorkspaceRunner - more output please

Related products:Transformers
  • August 3, 2017
  • 1 reply
  • 23 views

lifalin2016
Influencer
Forum|alt.badge.img+40

How about enhancing the output from WorkspaceRunner, e.g. by adding the workspace path and other relevant run information (time executed, number of features read/written), so it is easier to create a meaningsful output e.g. by email ?

When I have a complicated translation scenario, I utilize a "master" workspace, which spawns a number of "slave" workspaces. I would like to capture the ones that fail, and send myself an email with a list of which workspaces fail. As the workspace path is usually hardcoded in each WorkspaceRunner, the output is completely anonymous.

Cheers.

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

It would be great if a full log file could be created for each workspace ran by the WorkspaceRunner!