Pipeline doesn't exist on this workspace

[lfparaujo]

I'm having an issue with this new connection setting. 

I have this prod workspace and there is PL_Main and PL_Main_Legacy, when I try to change this on the trigger it's saying the pipeline that I'm trying to insert it's not in the workspace 

I have been trying for hours and still don't know what it can be. 

[lfparaujo]

Yes, I had to rename the pipelines but in some way the other engineer renamed back and it worked, so I'm still confused but the problem was solved. 

[v-huijiey-msft]

Hi @lfparaujo ,

Is my follow-up just to ask if the problem has been solved?

If so, can you accept the correct answer as a solution to help other members find it faster?

Thank you very much for your cooperation!

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

[v-huijiey-msft · Accepted solution]

Hi @lfparaujo ,

Thank you for sharing your solution, it will be of great help to those in the community who are experiencing similar problems.

If you had to rename the pipeline in one workspace to make it recognizable, you may run into similar problems when deploying to other workspaces.

You can develop a consistent naming convention, for example, by using a prefix or suffix to identify the use or environment of the pipeline, such as PL_Main_Prod or PL_Main_Dev.

If you have any other questions please feel free to contact me.

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

[lfparaujo]

update: for some reason, I had to rename a lot of Pipelines on this workspace to find it finally! the question is, what if I Deploy to other workspaces, is this gonna be an issue?