Error when importing an unmanaged solution - Error: "Solution: XXX imported successfully with warnings. The original workflow definition has been deactivated and replaced."

[CParsons09]

I recently started getting this "warning" message when importing my solutions from dev to any other environment. We haven't changed our ALM process so I'm confused as to why we are now seeing this. To make it even more confusing, if you refresh the solutions page, it changes to the green "imported successfully" notification. The log file does not provide any helpful details that I was able to translate.

Has anyone else seen this? Any ideas on what might be happening?

Note: these are unmanaged flows. (Yes, I know we should be using managed, but we are in a cleanup phase and haven't gotten all solutions migrated over to the proper ALM practice). 

[fchopo]

Hi @CParsons09 

I guess that your solution contains a workflow. Do you also receive this warning message if that workflow doesn't exist in destination tenant?

I assume it's a warning message stating that current workflow is being replaced by a new one.

Hope that helps!

Ferran

[techsan20]

My team just started recently in the last week getting this message with the same cadence where it appears, but then after refresh changes to imported successfully.  Ours is with managed solutions.  Our concern is that one of our developers says it changed the flow id and hence the url of the flow.  That could have major implications depending on how you referenced things.  On a normal solution import the id's would not change.   Anyone with more info or knowledge on this error and its cause would be great. 

[CParsons09]

I would say my environments started experiencing this last week as well, so the timing related to yours is very interesting. 

[CParsons09]

I'm not sure what you mean by "workflow"? It contains both a desktop flow and a cloud flow, but that hasn't changed. 

[EricZZZZ]

It is probably because you have a unmanaged layer,  which was created after imported as a managed solution. 

Remove the unmanaged layer this shall go away.

[CParsons09]

Unfortunately these solutions have been in the unmanaged state throughout all the environments, so I do not believe that is correct. 

[CParsons09]

Update: I just noticed I receive the same warning message when importing a managed solution as well. We haven't changed our ALM practice since noticing these warnings so I'm still leaning towards this being a bug but curious if anyone else has resolved it yet. 

[jatcube]

I did notice this warning message recently too on fully managed solutions.. as others pointed it out, the warning changes to success after a refresh. I noticed in the import log that the progress was reported as 90% completion, so the log is generated before the import has finished.

Also, in the log a flow reported the issue, then a second later the same flow with the same id is present without any warning. Seconds later, the same flow, same id reports as workflow activation successful.

Not entirely sure why it sends a warning, but since it changes to success a few seconds after, I personally wouldn't worry much.

That said, since the new update 2022 release wave 2 came out I occasionally get an annoying notification every time I want to save and retest my flow that someone else had modified the flow (I know no-one did) so could easily be just another feature (bug) introduced by MS - the update focuses on tighter governance and managed environments Microsoft Power Platform 2022 release wave 2 plan overview | Microsoft Learn

[CParsons09]

One thing to check if you have seen this problem, is desktop flow upgrades. I just noticed this morning that my production environment is not upgrading to the latest changes I made in the dev environment. The weird thing is my test environment does have those changes. I'm going to open a ticket with MS to see if they can help troubleshoot further as I have a number of desktop flows and am not concerned that they haven't been updating in prod for some time now. 

[CParsons09]

I opened a ticket with MS to investigate this further. Although it may not be a problem based on others comments, I feel it should still be looked at by MS. 

[KSomaya]

If this helps anyone but it did occur in one of my solutions (managed) where if you go in and change/edit > save a workflow (which you can in a managed solution) will automatically create a new unmanaged layer. This unmanaged layer can be viewed for individual objects in your solution (e.g. a workflow by clicking the three dots > advanced > solution layers. Here you will see that you have an unmanaged layer which is currently "Active" and blocking your solution upgrade to this specific object. Easy fix, select the unmanaged layer and Delete it if you have know that the upgrade has that fix/update in there. 

Now your ALM from Dev > UAT > Prod will not pop-up with any message hopefully. Good luck!

[Jeff_Thorpe]

@CParsons09 , what did you find out with the ticket you opened with Microsoft?

[CParsons09]

They are still researching the issue after I provided them the log files. 

[Vitss]

@CParsons09 please keep us posted.

[bcobra42]

I am also receiving this message in our environments.

[CParsons09 · Accepted solution]

I received final resolution on my open ticket with MS support. They concluded that this is simply a warning when existing workflows are being replaced and it will not cause any issues. See the screenshot attached. 

[jeff_ruel]

In our case, we get the warning and afterward, our flow is disabled (we have to reenable it) and all our connexions must be fixed, so it's not without issues.  Anyone has thev same symptoms ?

[johngootee]

The flow ids changing is the exact issue I am trying to figure out.  Did you get to any workaround on this?  The flows all work ok for me, but I have links that people have bookmarked to get to the flow to use it.  As run only users, the flows don't show up for them automatically, they have to have a link.

[EricZZZZ]

Hi johngootee,

I have switched to deployment pipeline to transfer unmanaged solution to managed ones. I strongly recommend you drop manual export/import and convert to deployment pipelines.