I am not sure what may be causing this issue, but I have made several attempts on running a pipeline after another has been executed. You can check them here and here.
Of course, reference to other pipelines may be sketchy in current API, but even hardcoding the files couldn't resolve the entire pipeline.
I am not sure what may be causing this issue, but I have made several attempts on running a pipeline after another has been executed. You can check them here and here.
Of course, reference to other pipelines may be sketchy in current API, but even hardcoding the files couldn't resolve the entire pipeline.