Re: PipelineCLI does not update workflow status when workflow is stopped on GUI
Here are results I received:
If I submit a workflow by PipelineCLI with -sync option, and at the same time monitor its execution under GUI, the Pipeline CLI loses the synchronization with DPS server. I guess that DPS server can keep synchronization for only one Pipeline client for each instance of a workflow. In this case, the client with GUI that I use for monitor.
Other wise, if I do not login to the Pipeline client GUI to monitor the active session, the PipelineCLI process stops as expected.
That can explain for my question in the first post of this topic that why the PipelineCLI does not stop when I stop the execution on GUI.
Could you please check it? If it is true, it is possible for DPS server having more than 1 Pipeline client instance for each workflow?
Thank you very much,