I have a Workspace (Child) which is supposed to runs as part of another Workspace (Parent). When I run the Child Workspace as standalone, it runs fine. But when I run the Parent Workspace, it never runs?
+4- Contributor
- 17 replies
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.
- 8392 replies
I believe you'll have to be more specific... What does the log say? Are there any features entering the WorkspaceRunner?
+4- Contributor
- 17 replies
Sorry david_r. The child WorkSpaceRunner is expected to load data from database X to database Y. The step previous to the child WorkSpaceRunner is an SQL Executor running a Stored Procedure to empty the database Y. On completion, the SQL Executor feeds Result value 1 to kickstart the child WorkspaceRunner.
But, somehow the run is not initiated and the Parent Workspace completes.
- 8392 replies
Sorry david_r. The child WorkSpaceRunner is expected to load data from database X to database Y. The step previous to the child WorkSpaceRunner is an SQL Executor running a Stored Procedure to empty the database Y. On completion, the SQL Executor feeds Result value 1 to kickstart the child WorkspaceRunner.
But, somehow the run is not initiated and the Parent Workspace completes.
What does the log say? Anything mentioning the WorkspaceRunner?
+4- Contributor
- 17 replies
I have attached image of the log file search results regarding the WorkspaceRunner. I couldn't make much sense of it. Hopefully, you can enlighten me.
- 8392 replies
I have attached image of the log file search results regarding the WorkspaceRunner. I couldn't make much sense of it. Hopefully, you can enlighten me.
I'm sorry, but there's too little context for me to get anything helpful out of this. If you cannot post more detailed information for confidentiality reasons, consider going straight to your FME reseller/partner for support, rather than using these public forums.
@ravibansal Sometimes this occurs if the parameters in the parent WorkspaceRunner are not passing as expected to the Child workspace. In your log file search out the lines:
INFORM|WorkspaceRunner
These will show you the parameters that were passed. There should also be a log file associated with the child workspace and this might also give you the clues you need to understand why the job failed.