Flow cannot be used as a child workflow because it is on an old version of Flow. Please re-create it inside a solution.

[hallsop]

Hi there all,

I've been trying to use the new child flows feature in the solutions environment. I have followed the instructions as described here, but when trying to add one of the flows it says "cannot be used as a child workflow because it is on an old version of Flow. Please re-create it inside a solution.". The flow is part of the solution, and I have even tried copying the logic to a completely new flow, but the error still occurs. Does anyone have any suggestions? (I've made sure the connectors are not using the run-only user)

[mrventerjaco]

I have the same issue, I did even create it in the Solutions page,  any updates on this?

[NickDewitt]

Getting the same thing here too.

One solution is to use the "Common Data Service (current environment)" connector only, but it seems that certain connectors/actions are causing this message to be displayed with no indication as to which element is causing the problem, the only way to figure it out seems to be trial and error.

[hallsop]

I think the issue could be to do with me using the approvals connector in the child flow, which is irritating as it is basically the only connector I need to use in it. The common data service connectors require a premium subscription don't they? I would happily carry on using http to run flows if they weren't making it premium. Is there anyone from microsoft who can elaborate?

[Anonymous]

Running into this same issue.  The flow was created new in the solution.  I've deleted every action in the child flow except for a variable initialization and I'm still getting the error.  Anyone find a resolution?

[CoreySutton]

I'm having the same issue. Has anyone found a solution to this?

[cattre]

No recent updates on this thread - did anyone find a fix in the end?

I decided to give it another go before remembering why I gave up the last time - argh!!!!

[hallsop]

Yep I gave up and have not since tried again. Ended up setting up some sharepoint lists that act as triggers for other flows (bit crude, but its working reliably!)

[stevethegray]

Having the same issue too, setting up another call with microsoft tech support, will update if they tell me anything useful.

Here is the full stack trace for posterity

Request to XRM API failed with error: 'Message: Flow client error returned with status code "BadRequest" and details "{"error":{"code":"ChildFlowsUnsupportedForNonOpenApiConnections","message":"The workflow with id '42595991-d2dc-ea11-a815-000d3a5a40b2', name Overdue Request For Engineering Assistance Process cannot be used as a child workflow because it is on an old version of Flow. Please re-create it inside a solution."}}". Code: 0x80060467 InnerError: Type: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]] Message: Flow client error returned with status code "BadRequest" and details "{"error":{"code":"ChildFlowsUnsupportedForNonOpenApiConnections","message":"The workflow with id '42595991-d2dc-ea11-a815-000d3a5a40b2', name Overdue Request For Engineering Assistance Process cannot be used as a child workflow because it is on an old version of Flow. Please re-create it inside a solution."}}". StackTrace: at Microsoft.Crm.Extensibility.OrganizationSdkServiceInternal.Update(Entity entity, InvocationContext invocationContext, CallerOriginToken callerOriginToken, WebServiceType serviceType, Boolean checkAdminMode, Boolean checkForOptimisticConcurrency, Dictionary`2 optionalParameters) at Microsoft.Crm.Extensibility.OData.CrmODataExecutionContext.Update(Entity entity, UpdateOption updateOption) at Microsoft.Crm.Extensibility.OData.CrmODataServiceDataProvider.UpdateEdmEntity(CrmODataExecutionContext context, String edmEntityName, String entityKeyValue, EdmEntityObject entityObject) at Microsoft.Crm.Extensibility.OData.EntityController.PatchEntityImplementation(String& entityName, String key, EdmEntityObject entityDelta) at Microsoft.Crm.Extensibility.OData.CrmODataUtilities.<>c__DisplayClass10_0`2.<InvokeActionAndLogMetric>b__0() at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute[TResult](ILogger logger, EventId eventId, ActivityType activityType, Func`1 func, IEnumerable`1 additionalCustomProperties) at Microsoft.Xrm.Telemetry.XrmTelemetryExtensions.Execute[TResult](ILogger logger, XrmTelemetryActivityType activityType, Func`1 func) at lambda_method(Closure , Object , Object[] ) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass10.<GetExecutor>b__9(Object instance, Object[] methodParameters) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary`2 arguments, CancellationToken cancellationToken) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ApiControllerActionInvoker.<InvokeActionAsyncCore>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__2.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Dispatcher.HttpControllerDispatcher.<SendAsync>d__1.MoveNext() InternalException: '.

[powerflows]

Have the same issue. Still no solution?

[ellean]

---

@powerflows wrote:

Have the same issue. Still no solution?

---

Nope. My guess is Microsoft updated something and isn't being open about it, as is typical, and so a bunch of us were left in chaos.

[ellean]

---

@stevethegray wrote:

Having the same issue too, setting up another call with microsoft tech support, will update if they tell me anything useful.

Here is the full stack trace for posterity

Request to XRM API failed with error: 'Message: Flow client error returned with status code "BadRequest" and details "{"error":{"code":"ChildFlowsUnsupportedForNonOpenApiConnections","message":"The workflow with id '42595991-d2dc-ea11-a815-000d3a5a40b2', name Overdue Request For Engineering Assistance Process cannot be used as a child workflow because it is on an old version of Flow. Please re-create it inside a solution."}}". Code: 0x80060467 InnerError: Type: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]] Message: Flow client error returned with status code "BadRequest" and details "{"error":{"code":"ChildFlowsUnsupportedForNonOpenApiConnections","message":"The workflow with id '42595991-d2dc-ea11-a815-000d3a5a40b2', name Overdue Request For Engineering Assistance Process cannot be used as a child workflow because it is on an old version of Flow. Please re-create it inside a solution."}}". StackTrace: at Microsoft.Crm.Extensibility.OrganizationSdkServiceInternal.Update(Entity entity, InvocationContext invocationContext, CallerOriginToken callerOriginToken, WebServiceType serviceType, Boolean checkAdminMode, Boolean checkForOptimisticConcurrency, Dictionary`2 optionalParameters) at Microsoft.Crm.Extensibility.OData.CrmODataExecutionContext.Update(Entity entity, UpdateOption updateOption) at Microsoft.Crm.Extensibility.OData.CrmODataServiceDataProvider.UpdateEdmEntity(CrmODataExecutionContext context, String edmEntityName, String entityKeyValue, EdmEntityObject entityObject) at Microsoft.Crm.Extensibility.OData.EntityController.PatchEntityImplementation(String& entityName, String key, EdmEntityObject entityDelta) at Microsoft.Crm.Extensibility.OData.CrmODataUtilities.<>c__DisplayClass10_0`2.<InvokeActionAndLogMetric>b__0() at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute[TResult](ILogger logger, EventId eventId, ActivityType activityType, Func`1 func, IEnumerable`1 additionalCustomProperties) at Microsoft.Xrm.Telemetry.XrmTelemetryExtensions.Execute[TResult](ILogger logger, XrmTelemetryActivityType activityType, Func`1 func) at lambda_method(Closure , Object , Object[] ) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass10.<GetExecutor>b__9(Object instance, Object[] methodParameters) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary`2 arguments, CancellationToken cancellationToken) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ApiControllerActionInvoker.<InvokeActionAsyncCore>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__2.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Dispatcher.HttpControllerDispatcher.<SendAsync>d__1.MoveNext() InternalException: '.

---

I tried to talk to a "Microsoft Expert" who is employed by the IT department and they were less than helpful. It felt like a complete waste of time. How was your interaction with the support folx?

[DennisTan]

Getting the same error. Can't find a solution for it anywhere.

[microsoftpower]

@DennisTan you should recreate your flow inside solutions again, then it will work. To do that quickly, use "Copy to clipboard" feature.

[AlexN]

Did exactly that, but it wasn't working at first.

But it turned out to be the SharePoint actions I was using and have copied where the root of the error.

Copying to clipboard in the old flow and pasting them into the new one didn't work, they where greyed out.

But some of my actions where nested in scopes and conditions, and those I could copy and paste without an error shown. But those SharePoint actions copied this way resulted in the error about having to recreate the flow.

[BenDaneliuk]

Hi Alex, did you resolve this issue.

I'm coming across the same problem.

I have re-created a new flow within the solution with no resolve.

[AlexN]

Yes, I could resolve it, but it was a pain in the ***

First of all, have you copied the actions by using the clipboard or have you created the complete flow as a new one including all the actions?
After it worked for me at first, I suddenly ended up with a non working flow. So I digged a little deeper and could see, that the code inside the actions of a working flow is different from the not working ones.

You can peek the code of the actions and it might look like this:

or like this:

See the differences? The first one won't work when used in a child flow, the second one will.

If you export the whole flow as json, you will see that the working actions are of type "OpenApiConnection", the others of type "ApiConnection" (at least this was it for me).

So what I did was to manually fix the actions of wrong format and it was working afterwards.

This was my "quick" fix yesterday, have to do some more checks and tests to see, how to prevent this from happening.

[SPONotification]

Did anyone found the solution for this issue, I have added flow to my solution and then created another flow to trigger  actual flow but I am getting same error.

did not have this issue in past.