Flow not available to add to solution?

[saturation]

I'm trying to locate a Flow I created outside of a solution to put into the solution, but it's not showing up in the list of Flows. What gives?

[rsaikrishna]

@saturation 

Some of the triggers or actions need to added properly to see them while adding the flows to solution.

Here is the blog which talks about it:

https://abesaldana.com/3-things-to-know-to-run-a-child-flow/

Add a new Action on the flow and select the Build-in actions when selected then click on the Flow icon and that will give you the only action to Run a Child Flow.

Regards

Krishna Rachakonda

If this reply helped you to solve the issue, please mark the post as Accepted Solution. Marking this post as Accepted Solution, will help many other users to use this post to solve same or similar issue without re-posting the issue in the group. Saves a lot of time for everyone.

[rsaikrishna]

@saturation 

What is the trigger of the flow which is not visible from solution? 

Here is another reason:

You may need to change the trigger to a different one temporarily and save the flow. Now, you will see the flow from the solution. 

Regards

Krishna Rachakonda

If this reply helped you to solve the issue, please mark the post as Accepted Solution. Marking this post as Accepted Solution, will help many other users to use this post to solve same or similar issue without re-posting the issue in the group. Saves a lot of time for everyone.

[rsaikrishna]

@saturation 

Here are few limitations:

• Button triggered flows are not available in solutions.
• Flows triggered from Microsoft 365 applications such as Excel are not available in solutions.
• Flows that connect to SharePoint are not available in solutions.

Button trigger flows: Change the trigger to different trigger. Once you see the flow in the solution, add it to the solution. Then, change the trigger.

Regards

Krishna Rachakonda

If this reply helped you to solve the issue, please mark the post as Accepted Solution. Marking this post as Accepted Solution, will help many other users to use this post to solve same or similar issue without re-posting the issue in the group. Saves a lot of time for everyone.

[saturation]

I did rebuild my child flow inside a solution and it showed up in the parent flow under the "Run a Child Flow" action now. However, I can't run the parent flow because I'm getting this error?

".... name YourFlow cannot be used as a child workflow because child workflows only support embedded connections."}}".

What does this mean?

[rsaikrishna]

@saturation 

Looks like your parent flow became your child flow? Child flows cannot be directly called.

Can check it? otherwise, try to re-add the action for Run a child flow.

Share here your findings.

Regards

Krishna Rachakonda

If this reply helped you to solve the issue, please mark the post as Accepted Solution. Marking this post as Accepted Solution, will help many other users to use this post to solve same or similar issue without re-posting the issue in the group. Saves a lot of time for everyone.

[saturation]

I didn't reverse the flows.... @rsaikrishna (they both sound like they are similar) But the full message is this when I run the parent flow. The child flow runs when I run it by itself.

 Error: Flow client error returned with status code "BadRequest" and details "{"error":{"code":"ChildFlowUnsupportedForInvokerConnections","message":"The workflow with id 'xxxxxxxxx', name Create Hyperlink URL cannot be used as a child workflow because child workflows only support embedded connections."}}".

[rsaikrishna · Accepted solution]

@saturation 

Without visibility into flow, it may be hard to provide recommendations. But, with the error you are receiving, there are numerous posts:

https://poszytek.eu/en/microsoft-en/office-365-en/powerautomate-en/quick-tip-flow-cannot-be-used-as-...

https://www.crmtechbits.com/cannot-use-child-workflow-because-child-workflows-only-support-embedded-...

https://powerusers.microsoft.com/t5/Building-Flows/Getting-error-calling-a-child-flow/td-p/430120

Can you please refer to above posts to see if any of them can help you resolve the issue?

Regards

Krishna Rachakonda

If this reply helped you to solve the issue, please mark the post as Accepted Solution. Marking this post as Accepted Solution, will help many other users to use this post to solve same or similar issue without re-posting the issue in the group. Saves a lot of time for everyone.

[packnology]

Adding to the list of triggers which for some strange reason prevent a flow created outside a solution from being added to a solution:

- "When a flow step is executed"

This is a serious limitation for re-use of flows with solutions. Deleting and re-adding a trigger which provides data to downstream actions will break the flow's functionality (all the references have to be re-entered) so it's not a great solution. With no ability to create private/internal templates in Power Apps, this makes developing flows very laborious.

Thanks,

Greg