I have configured a "master" workspace that runs 4 Workspace Runners sequentially. I run the master workspace from a BAT file via the fme.exe command line. When one child workspace fails, the parent workspace stops, but does not fail. The workspaces are linked together by the Succeeded port. The Failed port is not linked to anything. I imagine I should link it to something? If so what? Thanks.
Question
Workspace Runner: How do I make the parent workspace fail when the child workspace fails?
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.
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.
+26- Contributor
Or just do not connect anything to the FAILED port.
This way only on success of the child workspace the parent workspace will continue.
Be aware that a workspace only fails if an ERROR occurs. It will not fail if no output is generated by design or if a WARNING occurs!
+40- Contributor
Make sure your workspaceRunners are set to wait for job to complete: Yes. Connect a Terminator to the Failed port.
As Erik_jan notes, just because a workspace completes without errors, it does not mean that the expected results occured and you should continue processing. Some sort on interim validation is generally recommended.
If your interim workspaces are expected to produce a file you can check the existence of the file(via FileExistenceChecker custom transformer, or python) in the Succeeded stream between the WorkspaceRunners, while also connecting a Terminator to the Does_Not_Exist port.
+9- Contributor
Connect a Terminator to the Failed port, that should do the trick.
Thank you, I will try that.
+9- Contributor
Or just do not connect anything to the FAILED port.
This way only on success of the child workspace the parent workspace will continue.
Be aware that a workspace only fails if an ERROR occurs. It will not fail if no output is generated by design or if a WARNING occurs!
Thank you. I do not have anything connected to the FAILED port right now. My master/parent workspace is configured to run 4 workspace runners in sequence all connected by the SUCCEEDED port. Yes, thank you, I understand the workspace will only fail if an ERROR occurs in the log. That makes sense. Its good to know that a WARNING will not trigger a "fail".
+9- Contributor
Make sure your workspaceRunners are set to wait for job to complete: Yes. Connect a Terminator to the Failed port.
As Erik_jan notes, just because a workspace completes without errors, it does not mean that the expected results occured and you should continue processing. Some sort on interim validation is generally recommended.
If your interim workspaces are expected to produce a file you can check the existence of the file(via FileExistenceChecker custom transformer, or python) in the Succeeded stream between the WorkspaceRunners, while also connecting a Terminator to the Does_Not_Exist port.
Thank you. Yes I have my WorkspaceRunners set to wait for the job to complete. I will try to connect a Terminator to the failed port and see how that works for me. Thank you for the recommendations on validation. My interim workspaces are writing to an ESRI Geodatabase, not to files, but thanks for the suggestion. I'll keep it in mind for the future.
+9- Contributor
Connect a Terminator to the Failed port, that should do the trick.
Adding the Terminator to the FAILED port worked perfect. Thank you.
+10- Contributor
What if a featurewriter is used instead of a writer? Could we then trigger the terminator for a writer error?