Deployment Pipeline - Error when deploying from Dev to Test

[GTS_ONE]

Hi All,

So I was very excited to test the new Deployment Pipeline (long overdue!)

I was able to assign a Workspace to Development easily enough.  I published a single, very simple dataset/report there.

However, when I try to click the "Deploy to Test" button, I get this "Can't start the deployment" error as shown below.  I've double checked the list of requirements (being on Premium, being an Admin, etc) and everything looks fine.

Just wondering if anyone has seen something similar?

***********************

Can't start the deployment

There's a problem deploying the content. Please try again later. If the problem continues to occur, contact Power BI support.

Please check the technical details for more information. If you contact support, please provide these details.

• Activity IDd3db2972-52e8-4b8a-a51c-a8c73f96344a
• Request IDece4db23-9b9a-1593-f369-11b14ca07a29
• Correlation ID17d8d097-ed36-81cd-938f-b5cda55f216f
• TimeTue May 19 2020 07:22:41 GMT-0700 (Pacific Daylight Time)
• Service version13.0.13248.257
• Client version2005.1.00976-train
• Cluster URIhttps://wabi-us-north-central-redirect.analysis.windows.net/

[mark_carlisle]

If you're still having issues I've found that all datasets in the workspace must have the preview feature 

Store datasets using enhanced metadata format enabled, which does make sense when you think about what the Deployment Pipelines feature is doing.

This requirement does seem to be missing in the documentation though.

[Icey]

Hi @GTS_ONE ,

I can't reproduce your issue. It works well on my side.

Please check if the following conditions are met:

• You're a Power BI Pro user

• You belong to an organization that has Premium capacity

• You're an admin of a new workspace experience

And here is some deployment pipelines troubleshootings you can refer to. Hope it would help you.

If the content above can't help you troubleshoot the issue, and for it is a preview feather and just were enabled on 05/18, it is suggested to create a support ticket here to get a confirmatory answer.

Best Regards,

Icey

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Nimrod_Shalit · Accepted solution]

Hi,

we looked into your error. this is specifically caused since this feature is still rolling to production,

and it has some moving parts that are deployed with some delay.

This is what caused your bug.

Please try again in few days (should be fine by EOW).

if it still doesn't work, please reply here and we will further look into this.