Run a child flow error: ChildFlowMissingResponseOperation

[dom_benton]

Hi all,

Having some trouble relating to the Run a Child Flow action.

I'm running a flow that has a trigger of a Forms response > gets the responses from the Form questions > switches to call different child flows based on the answer from one of the questions in the Form. I have created a variable in the child flow's Manually trigger a flow trigger which is populated in the parent flow's Run a child flow action. When I save the parent flow, I get the error message below. Has anyone else had a similar problem? Do I need to pass anything back from child to parent?

Thanks.

Request to XRM API failed with error: 'Message: Flow client error returned with status code "BadRequest" and details "{"error":{"code":"ChildFlowMissingResponseOperation","message":"The workflow with id '79503a1f-2673-ea11-a811-000d3aba6633', name APAC request cannot be used as a child workflow because it is missing a response action."}}". 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":"ChildFlowMissingResponseOperation","message":"The workflow with id '79503a1f-2673-ea11-a811-000d3aba6633', name APAC request cannot be used as a child workflow because it is missing a response action."}}". 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.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: '.

[ChristianAbata]

hi @dom_benton to run child flows you need to consider this two conditions.

1. The parent flow: This flow can have any type of trigger and will call into the other flow.
2. The child flow: This is the flow that is nested inside the other flow and contains the smaller tasks you want to run.

Here is the doc where you can find more details about your error.

https://docs.microsoft.com/en-us/power-platform-release-plan/2019wave2/power-automate/call-child-flo...

[dom_benton]

Thanks @ChristianAbata. I've already built the parent and child flows but i'm unsure why i'm getting this specific error message as displayed in my original post. As it's such a new feature there doesn't seem to be much support for errors so any assistance would be greatly appreciated 

[JohnAageAnderse · Accepted solution]

Hello @dom_benton 

In the reference that @ChristianAbata  gave you is stated that the child flow must respond to the parent flow. In the documentation that should be one of these actions:

1. Respond to a Power App or flow (under the Power Apps connector).
2. Response (on the premium HTTP request/response connector).

Does your child flow have such?

Kind regards, John

[dom_benton]

Thanks @JohnAageAnderse i didn't have a pass back action once i added that it worked.

Thanks