โ07-28-2020 08:48 AM
We have a requirement to create many different scheduled tasks for different clients, but they will all be executing the same pipeline.
For clarity weโd like to keep tasks for each client in their own project space, but the task scheduler UI requires that the pipeline is in the same project space.
Iโve tried updating the task with the meta snaps, which seems to work but opening the task in the UI says โpipeline has been deletedโ
Is it possible to create a scheduled task which runs, for example, โโฆ/pipeline_nameโ or โ/shared/pipeline_nameโ or โORG/project/pipelineโ ?
โ07-30-2020 11:59 AM
At the moment Tasks can only reference pipelineโs in the same project. There could be certain features that wonโt work if you use the metadata snaps to modify the task reference.
You might be able to work around the limitation by using a Pipeline Execute snap, which can trigger a pipeline by name within the same project, the project spaceโs shared project, or the orgโs shared project.