Microsoft Dynamics 365 | Integration, Dataverse...

Trying to Deploy Managed solution Facing ImportAsHolding Error

(1) Share

Report

Posted on by RS-17071718-0

Hi Community

I was Trying to deploy the managed solution from Dev to Test Env, but faced the below error message issue multiple times with 2 different cloud flows while running the deployment pipeline.

The reason given was: ImportAsHolding failed with exception :Error while importing workflow {3b15c139-e712-ef11-9f89-6045bd063812} type ModernFlow name Flow_Name: Flow server error returned with status code "ServiceUnavailable" and details "{"error":{"code":"ServerTimeout","message":"The request timed out. The tracking Id is 'tracking guid'."}}".

Can anyone please help me in how to navigate this issue.

Appreciated!!

Thanks

Categories:

Dynamics 365 general

Power Platform integration

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Sagar121 1,196 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

publish your customization first then re-try

Was this reply helpful? Yes No
Suggested answer

11manish 1,259 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!
The error indicates that the solution import reached the ImportAsHolding stage, but the Modern Cloud Flow failed to import because the Power Automate service returned a ServerTimeout (ServiceUnavailable). This is commonly a transient service-side issue rather than a problem with the solution itself.

Here are a few things you can check:

Retry the deployment after some time, as temporary service interruptions or high platform load can cause timeouts.

Check the Power Platform Admin Center and Microsoft 365 Service Health for any ongoing incidents or maintenance affecting Power Automate or solution imports.

Verify that the target environment is healthy and not undergoing maintenance.

Ensure all connection references, environment variables, and required connectors are present and properly configured in the target environment.

Confirm that the deployment account (user or service principal) has the necessary permissions to import solutions and create/enable cloud flows.

If the affected flow is particularly large or complex, consider simplifying it or splitting it into smaller flows, as long-running imports are more susceptible to timeouts.

Try importing the solution manually through the Power Apps Maker Portal. If the manual import also fails with the same timeout, it further suggests a backend service issue rather than a deployment pipeline configuration problem.

If the issue consistently occurs with the same flow,raise the Microsoft Support request.

Was this reply helpful? Yes No