Invoke Pipeline Activity Requires Connection to Workspace (Mandatory)

It's counter intuitive to require the Invoke Pipeline Activity to have a connection property to a workspace, as mandatory, given that in most cases the pipeline should be in the current workspace and therefore the child pipeline could just run as the executor of the current pipeline. Is there a workaround that people have found to accomplish this? Is there some reason why it has to be this way specifically? submitted by /u/Personal-Quote5226 [link] [comments]