unable to trigger manual workflow due to "The workflow '734d...' could not be found."

[starecek]

I am using a managed solution for all tables in project and an unmanaged solution to deploy/develop data-load workflows to load data for these tables. The solutions are deployed to a dataverse for teams environment.

When trying to trigger the flow the following error-message is displayed:

   The workflow with the id '734d...' could not be found.

The reported id in the error-message does not reflect the id of the workflow. I have downloaded and unzipped the solution and I cannot find the reported workflow id in the code.

When saving the flow to myflows (using the saveas) the flow triggers and runs as expected.
I appreciate any thoughts and support how to fix this error or how to get to the root-cause.

[leo85]

When you change a flow in a managed solution, it creates an unmanaged layer. This also results in a new flow id. So check if the flow has an unmanaged layers.

[guenthi]

thanks for the hint leo85 - all the flows are part of an unmanaged solution and when the unmanaged solution containing these flows is imported in the environment all flows land in the unmanaged layer. After importing and starting the flow I get the following error - the flow-id in this message does not correspond to the one I have imported

[MarrinerDev]

Any luck finding a solution to this?

[guenthi]

@MarrinerDev , unfortunately not yet. Sometimes I still experience this with new environments.

Currently the only way to resolve this, is re-provision a new environment with importing all the affected data.  

[sammysword]

I too am experiencing the same issues. It's not feasible to constantly provision new environments or to delete solutions and re-install them, which even then doesn't always work.

Has anyone managed to get a fix for this?

[crmvet]

I had this issue installing a solution with flows in a freshly restored environment. So, I've installed flow; connections were auto-selected for connection references of that flow (connections probably were not existing as backup restore should have erased them). So I deleted connections and created new, updated connections referenced for them, and it fixed the error.

[sammysword · Accepted solution]

I had a call with Microsoft around this. The explanation given was that when you import a Managed solution with workflows, it creates a link to Azure for each of these and generates an ID. If you then delete the solution, it will delete from the Power Platform side, but the Azure ID still exists. When you try and then import the same solution back in, it then cannot re-associate to the existing Azure ID and the process breaks. I have found that if my flows are run by HTTP requests or are Child flows, these will still work as long as they are not manually invoked.

The advice I was given was if possible to create a new environment and then ensure I do not delete solutions. It is something they are aware of as a bug though and are trying to fix.

[starecek]

Thanks for your feedback, @crmvet - for manually triggered flows I have saved a copy in myflows and then I could run the flow. 
Changing the flow in the solution, like adjusting connection will create a unmanaged layer, which will cause that you have to undo and redo this fix every time you update the flow. I have delete and recreated the environments with the initial data 

[starecek]

@sammysword , thanks for clarifying and sharing