Error due to cloned Pipeline after it was renamed and has been published

Greenwood, Justin 0

Hi all I cloned a pipeline and then renamed it and published the changes: So Now I have

FolderLive

PipelineLIVE
PipelineTEST

FolderTEST

Perfect! so all published and ready for the next step of moving PipelineTEST in to FolderTEST and publish.

Error code: OK

Inner error code: BadRequest Message: The operation failed because the entity 'PipelineLIVE' is being renamed to 'PipelineTEST'. A retry of rename from exact source to target may work.

Now I can not do any thing with the original or the cloned pipelines.

Can someone please help me resolve this issue?

Chandra Boorla 2,680 Reputation points Microsoft Vendor

2024-07-26T08:30:29.1433333+00:00

Hi @Greenwood, Justin

Just checking in to see if the below answer helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Chandra Boorla 2,680 Reputation points Microsoft Vendor

2024-07-30T12:49:55.0233333+00:00

Hi @Greenwood, Justin

Following up to see if the below suggestion was helpful. And, if you have any further query do let us know.

1 answer

Chandra Boorla 2,680 Reputation points Microsoft Vendor

2024-07-24T14:39:21.2+00:00

Hi @Greenwood, Justin

Thanks for the question and using MS Q&A platform.

It appears there is an issue with renaming pipelines in your pipeline management system. The error message indicates a conflict arising from an attempt to rename PipelineLIVE to PipelineTEST.

As I understand that, you have cloned a pipeline, renamed it, and published the changes. You are now attempting to move the cloned pipeline (PipelineTEST) into a new folder (FolderTEST) and publish it again.

To address this issue, I recommend retrying the renaming process from the exact source to the target. This may help the system correctly rename the pipeline and resolve the conflict.

Additionally, consider temporarily renaming the PipelineLIVE pipeline to a different name. Then, move the PipelineTEST pipeline into the FolderTEST folder. Once the pipeline has been successfully moved, you can rename the original pipeline back to its initial name.

Hope this helps, please do let us know if you have any further questions.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Please sign in to rate this answer.
Greenwood, Justin 0 Reputation points

2024-07-25T10:28:28.1566667+00:00

HI @Chandra Boorla

So:

Renamed PipelineTEST to Pipeline = Same error on publishing

Renamed PipelineLIVE to Pipeline = Same error on publishing

Renamed FolderTEST to Folder = Same error on publishing

Deleted PipelineTEST = Same error on publishing

Deleted PipelineLIVE and PipelineTEST = Same error on publishing

Chandra Boorla 2,680 Reputation points Microsoft Vendor

2024-07-25T12:37:03.99+00:00

Hi @Greenwood, Justin

In case your Synapse workspace is GIT configured, to maintain code integrity and facilitate efficient collaboration, we recommend creating a new local branch for modifications rather than directly editing the collaboration branch. Once changes are complete, rename the pipeline and submit a pull request to merge the updates into the collaboration branch.

For more details, please refer to the similar thread: https://learn.microsoft.com/en-us/answers/questions/1325818/how-to-resolve-publish-errors-on-azure-synapse-whe

For additional information, please refer: https://learn.microsoft.com/en-us/azure/synapse-analytics/cicd/source-control#best-practices-for-git-integration

I hope this information helps, please do let us know if you have any further queries.

Greenwood, Justin 0 Reputation points

2024-07-26T09:46:22.69+00:00

It is not GIT configured

Chandra Boorla 2,680 Reputation points Microsoft Vendor

2024-07-29T11:43:07.6833333+00:00

Hi @Greenwood, Justin

Apologies for the inconvenience that you are facing.

It's possible that orphaned resources or dependencies are causing the conflict. To resolve this, please carefully examine the following components for any references to the old pipeline names that might help you:

Linked Services: Ensure no connections rely on the previous pipeline names.

Datasets: Verify that datasets are not dependent on the old pipeline outputs.

Triggers: Check if any triggers are configured to monitor the old pipeline.

Notebooks and Data Flows: Inspect these components for any references to the deleted pipelines."

For additional information please refer the below links:

Link1: https://medium.com/@morsi.masmoudi/azure-finops-how-to-remove-orphaned-resources-and-save-costs-7ff52492f897

Link2: https://techcommunity.microsoft.com/t5/fasttrack-for-azure/azure-orphan-resources/ba-p/3492198

If the issue still persists, please do let us know. Glad to help.

I hope this information helps.

Chandra Boorla 2,680 Reputation points Microsoft Vendor

2024-08-01T13:41:52.44+00:00

Hi @Greenwood, Justin

Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Error due to cloned Pipeline after it was renamed and has been published

1 answer

Your answer