topic Re: Deployment pipeline error - not bound in Data Engineering

Deployment pipeline error - not bound

ebjim — Tue, 25 Jun 2024 02:02:31 GMT

I have a deployment pipeline that connects two workspaces. I am trying to use it to deployment a data pipeline and get got this error:

Deployed items with the same name in the target and source stages are not bound. This may be due to recent actions, such as deleting or adding new items, still being in process.

I have searched for answers, especially in the context of data pipelines (not Power BI), but came up empty. Any ideas would be appreciated. Thanks in advance!

Re: Deployment pipeline error - not bound

chetnachaudhari — Wed, 26 Jun 2024 03:06:48 GMT

@ebjim Did you manage to resolve this? I started noticing same error today when tried to deploy items from one workspace to another. Its coming for all sort of items, like environment, lakehouse, notebook and data pipelines

Re: Deployment pipeline error - not bound

chetnachaudhari — Wed, 26 Jun 2024 21:05:10 GMT

We noticed that the issue was resolved once the running pipelines finished their active run. We were able to deploy from one workspace to another when the items involved in deployment were in idle state.

Thanks,

Chetna

Re: Deployment pipeline error - not bound

v-cboorla-msft — Mon, 01 Jul 2024 05:43:10 GMT

Hi @ebjim

Thank you.

Re: Deployment pipeline error - not bound

v-cboorla-msft — Tue, 02 Jul 2024 05:23:39 GMT

Hi @ebjim

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. If you have any question relating to the current thread, please do let us know and we will try out best to help you. In case if you have any other question on a different issue, we request you to open a new thread.

Thank you.

Re: Deployment pipeline error - not bound

mybarbie9917_LI — Mon, 29 Jul 2024 20:22:52 GMT

This happened to me. I created a folder in my "Dev" workspace to move my report to that folder. When I tried to deploy that report from "Dev" to "Test" workspace, I encountered the same error message "Deployed items with the same name in the target and source stages are not bound. This may be due to recent actions, such as deleting or adding new items, still being in process.".

After 2 days of struggle, I solved the issue by simply moving the report out of the folder in the "Test" workspace, then continued with the normal deployment procedures. I'm not sure about the technical aspect behind the scenes, but I hope it helps.

Re: Deployment pipeline error - not bound

VJKR — Wed, 07 Aug 2024 00:53:01 GMT

I has fixed the issue by simply moving the report from the folder to the worspace and run the Deployment Pipeline. It worked.

Re: Deployment pipeline error - not bound

Talkas — Mon, 21 Oct 2024 14:25:50 GMT

Hello, I was able to solve the issue, just by not creating the folders in the target workspace, but letting the system to create them by it self when moving from one workspace to another.

Re: Deployment pipeline error - not bound

Smokey66 — Tue, 19 Nov 2024 09:52:06 GMT

How long did you have to wait? I encounter the same issue and moved the report out of the folder but still face the same issue

Re: Deployment pipeline error - not bound

Smokey66 — Tue, 19 Nov 2024 09:52:33 GMT

How long did you have to wait? I encounter the same issue and moved the report out of the folder but still face the same issue

Re: Deployment pipeline error - not bound

carloscantu — Thu, 09 Jan 2025 21:37:57 GMT

That worked for me as well, thanks for sharing this workaround!

Re: Deployment pipeline error - not bound

swientzek_irs — Mon, 04 Aug 2025 09:07:12 GMT

Thank you for the hint, this resolved my problem.

Re: Deployment pipeline error - not bound

EgregorypG — Thu, 28 Aug 2025 16:48:16 GMT

I'm having the same issue, any updates on this topic or alternatives provided by Microsoft?

Re: Deployment pipeline error - not bound

gpalsson — Mon, 01 Dec 2025 12:43:55 GMT

incredible that this is still an issue while MS is continually pushing new shiny "features" and almost everything about CICD is just broken.