You’re offline. This is a read only version of the page.
Greetings,
I developed a Power Automate solution that uses several child flows. I exported the solution from my DEV environment and successfully deployed to UAT and PROD environments where it has been running for several weeks. I recently added additional functionality to the solution that includes two new child flows. I exported the solution and successfully imported it to the UAT environment and completed testing. I then imported the solution into the PROD environment where I get the following error message when I try to turn on the main flow:
In case that screenshot is not readable, it says:
Share
ReportFlow client error returned with status code "Bad Request" and details "{"error":{"code":"ChildFlowNeverPublished","message":"The workflow with the id '[GUID]' 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."}}".The flow id refers to one of two child flows added to the solution to support the new functionality. The solution works in the UAT environment. Only in the PROD environment do I see this error.
I have re-exported (with the publish step) and imported the solution several times but have not been able to resolve the issue.
Thanks in advance for any assistance.
I just had the same problem, with a chain of 5 flows. I think the import might just be trying to turn the flows on in the wrong sequence, and then leaves all or most flows turned off. When I turn them on starting "bottom-up" everything works - which I of course only found after many exports and imports.
Hi, Kim,
The issue for me turned out to be that one of the child flows was importing into the PROD environment with Status = Off. Once I turned the child flow on, the solution worked as expected.
Needless to say, the error message was not helpful in diagnosing the problem. I hope this helps.
Hi @KimLeGrand
If your situation is the same as mine, you need to import your full solution from your sandbox to production environment. You would take your base solution in sandbox (the solution that has the patches in production) and clone solution. This will package up the base solution and patches in sandbox and leave you with a new, full solution. Export this new solution version and import into production. This will remove the patches and leave you with the new, full solution...which should resolve your issue (if the same).
Good day,
I have the same issue. @MarcusCadena can you explain further how to get fully updated solution ?
Thanks
This is probably too late to help you, but hopefully it will help someone else.
I encountered this error in a similar scenario. Parent Flow with two child Flows, which could be enabled and worked fine in our sandbox environment. However, once the solution was moved to our production environment this same issue occurred.
For my situation, this was occurring while there were solution patches present in production. Once a fully updated solution was imported into production this error did not occur. I was able to turn on the parent and child Flows without errors.
#1
Tomac
986
Moderator
#2
stampcoin
699
Super User 2025 Season 2
#3
Riyaz_riz11
577
Super User 2025 Season 2
All responses (
Answers (