Child workflow not available from parent workflow to invoke unless saved (Logic App Standard workflows zip deployed)

Question

I have a Logic App Standard instance in our dev environment that has a parent workflow which calls the Invoke workflow action which calls a child workflow.

I deployed to prod using via a zip deploy using the Azure cli.

The workflow's all show up in the production Logic App Standard. However, if I try to run the parent workflow I get an error saying both the Parent and Child workflows need to be in the same Logic App.

After troubleshooting I found that if I made a change to the child workflow, hit save via the portal designer, and then ran the parent workflow it worked.

Seems like the act of saving the child somehow registers it and makes it callable by the Parent.

Is there a way to "Save" the work flow via an API instead of having to manually do it?

Thanks,

Mike

Answer 1

Hello, @Mike Lee Thanks for reaching out, and posting on MS Q&A.

Regarding:

Is there a way to "Save" the work flow via an API instead of having to manually do it?

Portal is a UI for the ARM so there's probably a PATCH/POST request that does the "Save" operation against an ARM endpoint. In these situations, I use the browser's DevTools and its Network tab to capture the exact request and then reconstruct it with the required AAD token in any automation work. I hope the same trick can be of help to you here in the short term.

The bigger issue is that you shouldn't have to do the above though. To expand & confirm, 2 workflows are nested using Azure Logic Apps action (where "type: Workflow" in CodeView) and both are created under the same Logic Apps works as expected on a Dev environment. However, when re-deployed to a different/prod environment, they appear no longer under the same Logic Apps (and throw an error stating so) until you have to manually save the child workflow in Portal which implicitly gets them "in-sync" again? If that is correct, a couple of considerations:

• Create workflows that you can call, trigger, or nest using HTTPS endpoints in Azure Logic Apps documentation appears to be for Logic Apps Consumption only.
• If your Child workflow runs on a Request trigger, could you try calling it using the normal HTTP action instead of using the Azure Logic Apps action?

---

Please "Accept Answer" if the answer is helpful so that others in the community may benefit from your experience.