Unanswered

Solution Import failed. Getting error - Error while importing workflow {id} type ModernFlow name Chg_tblStandard

(0) Share

Report

Posted on by User3336

I am trying to import a unmanaged solution on an environment but receiving the error - Error while importing workflow {22d1c07b-6ba7-ec11-983f-00224826dbde} type ModernFlow name Chg_tblStandard: Flow server error returned with status code /InternalServerError/ and details /{/error/:{/code/:/InternalServerError/,/message/:/Http request failed with unhandled exception of type 'Exception'.

Tried again and got the error again but with a different power automate. There has been no modifications made to the automate since past few months. How can this be resolved?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (6)

Answers (0)

Michael E. Gernaey 53,345 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

Unfortunately, You will have to open a ticket with support for this issue.

Cheers
If you like my answer, please Mark it as Resolved, and give it a thumbs up, so it can help others
Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

Was this reply helpful? Yes No
shanelewismi 4 on at

Like (0)

Report

RiyaKaul, did you find out what caused this error and/or a solution? I am getting the same error about a Workflow that has not been changed in months and seems to be working properly

Was this reply helpful? Yes No
User3336 41 on at

Like (0)

Report

Not resolved.

Was this reply helpful? Yes No
ivan_apps 2,187 Moderator on at

Like (0)

Report

In the solutions section there is a ‘history’ tab that shows import history. Check there and see if it shows more details about your error.

try to isolate or remove the flows from the rest of the solution and re-import. Since it’s unmanaged solutions you should be able to break up the solution into as many parts as needed to see which flow is the error one.

Was this reply helpful? Yes No
mdvd02 2 on at

Like (0)

Report

Could it be that you are not an owner on the flow in the environment in which you are trying to import? I'm getting a similar error and I believe becoming an owner of the flow resolved my issue. I need to confirm as I'm getting different errors now. But worth confirming that.

Was this reply helpful? Yes No
shanelewismi 4 on at

Like (0)

Report

I was able to solve this issue by removing all Flows from the solution, which then caused some other errors on import (strange Teams entity errors) that is not used as part of the solution, so this was removed from the solution as well. Imported into Production successfully, added the Flows back into the solution and imported again to Production successfully. No issues since.

Was this reply helpful? Yes No