Nesting a pipeline under another can cause it to be omitted from the run page

[augray]

To reproduce:

• create a Sematic func at some path (ex: foo.bar.baz)
• execute it as the root function
• verify it now shows up on the pipelines page
• create a new Sematic func that calls the prior one (ex: foo.bar.parent calls foo.bar.baz)
• execute this new wrapper as the root function
• the original func (foo.bar.baz) no longer shows up anywhere on the pipelines page