From a cost perspective, does it make more sense to have a complex flow that has multiple yes/no conditions checking multiple records and sending Teams messages based on the conditions being met. Or to separate into multiple flows which would pull the same records?
My flow is a scheduled flow which runs daily, checking the status + due date of a record. Based on the combination of these two:
If status = X and Due Date = today - send message
If status = X and Due Date = - 6 days - send message
If status = X and Due Date = + 30 days - send message
If status = X and Due Date = + 30 days - send escalation
I am not sure from a pricing perspective if the more complex my flow is, the more expensive it becomes and it would make sense to split into two flows. Or if having multiple flows would be more expensive. Or if the cost is the same.
I would also have another flow that would be scheduled to run once monthly to send a reminder for all with
status = X - send message
Screenshot of the flow that will have the 4 messages. This is only show the first two messages.
Solved! Go to Solution.
Hi @DiFritz ,
If you are putting up so many actions in one flow and depending upon the number of records you are processing via flow will decide if you need to split your flow into multiple or not. Ideally if you are going to perform same action on different records via different routes better to have one child flow and call it from your parent flow.
Thank you for your feedback. My flow is a scheduled flow, which runs daily, as it will run through many records to see which meet the conditions. It is my understanding that a scheduled flow cannot be in a Solution, and Parent/child Flows must be in Solutions? Therefore I could not use the Parent/Child functionality - am I correct?
Keep up to date with current events and community announcements in the Power Automate community.
A great place where you can stay up to date with community calls and interact with the speakers.
Check out the latest Community Blog from the community!