In this Power Automate related post I'm going to go over
Mentions to Pieter Veenstra in this post to link to one of his posts on how you can link your child flows up to find the parent flow that triggered them in their run history for even easier debugging and error handling!
When you have used child flows and attempted to debug issues you will have come across the issue where you want to find the parent flow for the failing child flow.
Power Automate (formerly known as Microsoft Flow) is a cloud-based service that helps you automate repetitive tasks and workflows across your applications and services.
A child flow is a standalone flow that can be called from within another flow. Child flows allow you to modularize your flows and reuse common functionality across multiple flows. This can make your flows easier to manage and maintain, as you can update the child flow and have those changes reflected in all of the flows that call it.
To create a child flow, you first create a standalone flow as you normally would, and then save it. You can then use the "Call a child flow" action in any other flow to call the child flow and pass data to it as inputs. The child flow can perform its actions and then return data back to the calling flow using outputs.