Deployment error when using pipeline from Dev to Test

[tankepaus]

Getting an unspecified error on deployment from Dev to Test.

I am admin on both workspaces. I am the dataset owner of the datasets being replaced in Test (also owner in Dev). The workspaces are part of the new workspace experience and datasets are v3. We have Premium capacity. 

Power BI service error message (pops up after a couple of minutes):

Something went wrong
The action can't be completed.
Please try again later or contact support. If you contact support, please provide these details.
Activity ID: 90b84881-74a6-4723-b3f3-70514a9214ef
Request ID: 14640064-2c19-d5c3-d658-61154c9cf179
Correlation ID: 0b6152c0-affd-0d7b-0055-1eebb08df8f3
Time: Mon Aug 17 2020 15:20:03 GMT+0200 (centraleuropeisk sommartid)
Service version: 13.0.14066.71
Client version: 2008.1.02249-train
Cluster URI: https://wabi-us-east2-redirect.analysis.windows.net/

Chrome DevTools shows HTTP 500 error on the URLs

https://wabi-us-east2-redirect.analysis.windows.net/metadata/almpipelines/1219/stages/1/diff
https://wabi-us-east2-redirect.analysis.windows.net/metadata/almpipelines/1219/stages/2/diff 

The caller that generates the error is https://content.powerapps.com/resource/powerbiwfe/scripts/powerbiportal.dependencies.externals.bundl...

Any ideas are greatly appreciated 🙂 

[Anonymous]

HI @tankepaus,

I'd like to suggest you check the official document to confirm if your scenario meets the limitations lists:
Understand the deployment process (preview)#limitations 

Regards,

Xiaoxin Sheng

[tankepaus]

Thank you for your reply @Anonymous 

I've re-checked the limitations but still it does not work.

[tankepaus]

Now the deployment shows success then minutes later it shows failure. And the deployed datasets (not source) are now corrupted.

I know the feature of deployment pipelines is in preview.

[Nimrod_Shalit · Accepted solution]

Hi @tankepaus,

i would receommend to open a support ticket in these cases to properlly check the root cause.

specifically here, we've looked into your error details-

looks like your capcity was overloaded, which impacts both the 'compare' operations and the deployment of content.

it is recommended to deploy content in times where your capacity is not in full use, to prevent an overload and errors for the above operations.