Deployment Pipeline runs for several hours then errors out with generic error message

[larssonhampus]

We've been using Deployment Pipelines since April without any issue but since the 12th the Pipeline we use has started running for several hours and then terminating with a generic error message saying:

"Deployment was stopped

Deployment couldn't be completed."

"No tracking information available."

There are no new reports we are trying to deploy and it's only small visual changes we are trying to deploy. The current run has been running for over 6 hours and I can't find a way to terminate it.

I can't see anything related to the Deployment Piplines in the Fabric Monitoring tab, is there anywhere else you can get more information about what is going wrong?

And what could be causing this behaviour?

[tayloramy]

Hi @larssonhampus, 

What types of items and how many items are in your workspace that you're trying to deploy? 

If you have hundreds of items, you might want to do a selective deployment and deploy them in batches so that the deployment pipeline doesn't time out. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution. 

[larssonhampus]

Hi @tayloramy ,

It was just a single report we were trying to deploy.

[tayloramy]

Hi @larssonhampus, 

Interesting, that should not happen. I recommend opening a ticket with Microsoft. Something is wrong and I think more telemetry data from your tenant will be required to troubleshoot. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution. 

[Ugk161610 · Accepted solution]

Hi @larssonhampus,

We’ve seen this exact behaviour recently as well. Our Deployment Pipeline runs that used to finish in a few minutes suddenly started dragging on for hours and then failing with the same generic “Deployment was stopped / No tracking information available” message. Nothing in the workspace had changed and we weren’t deploying anything large — just small report updates.

From what we noticed, this usually isn’t caused by anything in your workspace or your deployment rules. It seems to happen when the Fabric backend gets stuck trying to validate or sync one of the items in the pipeline. The run doesn’t actually fail immediately — it just waits indefinitely until Fabric times out the entire deployment operation. That’s why you see a long-running job with no status updates and no monitoring details.

We weren’t able to cancel the run either. The UI doesn’t currently offer a way to force-stop a blocked deployment, so we had to wait it out and try again later. In our case, the next run eventually succeeded without us changing anything at all, which made it pretty clear that the problem was on the service side rather than our environment.

At the moment, the Monitoring tab unfortunately doesn’t give any useful logs for Deployment Pipelines. So if the run doesn’t surface an error inside the pipeline itself, you won’t see anything more than the generic failure message you already got.

If the issue keeps happening for you, it’s worth re-trying after a while or even re-opening the workspace to get past any stuck state on the backend. We had a couple of days where deployments were unstable, and then everything went back to normal on its own.

Hopefully Microsoft improves the logging around this soon — the generic “Deployment was stopped” message doesn’t give much to work with.

– Gopi Krishna

[larssonhampus]

Hi Gopi,

Thank you for your reply!

It seems we were experiencing the same issue as you described, the pipeline timed out over the weekend and I can run it like normal again this morning.

Cheers,

Hampus