CODEWITHSUNDEEP
power-automatepower-platform
BladeZ
BladeZ

Reputation: 217

Power Automate error when trying to turn on child flow

I am trying to install Business Approval Kit to my production environment.

I am almost done with the installment. The last step should be turning on all flows that come with the solution. But for some reason turning child flows on results to this error:

Turn on failed. Flow client error returned with status code "BadRequest" and details "{"error":{"code":"ChildFlowNeverPublished","message":"The workflow with id '613b8c18-5ad4-ec11-a7b5-000d3af4ac06' cannot be used as a child workflow because it has never been published. Child workflows need to be published at least once before they can be included in a published parent workflow."}}".

This error doesn't make any sense to me, because this should be a production ready solution from Microsoft.

According to Microsoft documentation flows should be turned on in a specific order, otherwise there might occur some other errors. The official Microsoft list can be found here: https://learn.microsoft.com/en-us/power-automate/guidance/business-approvals-templates/setup#activate-the-core-cloud-flows

I get some of the first flows turned on but got stuck in the first child flows. Picture below showing the situation.

Current state of the issue

Any Power App/Automate pro knowing how to fix this issue?

Upvotes: 0

Views: 37

Answers (1)

Laviza Falak Naz
Laviza Falak Naz

Reputation: 446

Child Flows or even base flows are turned off if they are HTTP Triggered. All child flows are HTTP triggered by default. It is because the URL changes when the flow is moved across environments. You will need to open the flow and simply publish it to generate the new URL and then update any flows that call this child. Otherwise, it will never be called.

At our place, We maintain a repository of URLs and the flows fetch child URLs directly. So when the solution is moved, we do not update the production flows. We only retrieve the URL of newly deployed flows and update our repository. The flows continue to work as they find the required URLs from the repository.

Upvotes: 0

Related Questions