Unanswered

Process mining in one big flow vs multiple child flows

(0) Share

Report

Posted on by Bob13

Hi all,

I am currently working on creating a big flow for automating an important process in our company. I have a choice whether to make one bog flow, or multiple child flows. I like the new process mining functionality in Power Automate and I was wondering if this function would work if I divide my big flow into multiple child flows. What would you guys suggest? Create one big flow (so that the process mining definitely creates accurate data) or create multiple flows (and risk that the process mining functionality may not be perfect)

Categories:

Process mining

I have the same question (0)

All responses (2)

Answers (0)

YaminiBharathiK 62 on at

Like (0)

Report

Hi,

So according to my opinion it entirely depends on the project calculations and data.

I've created such flows, For my project it demand multiple flows instead of one Single flow.

Multiple flows benefits,
1) If your business logic has so many conditions then better go with multiple flows. Power Automate has a restriction with nested conditions and you can't go beyond nesting limit 8.
2) The oops principle if you can break it in a structured way , may be the flow can be used in other area if required. Like taking backup file/sending mails/reports sharing etc.,
3) The debugging makes it easy compared to one big flow, where you have to check back and forth values.
4) Accuracy can also possible if you have data design planned.

Thanks.

Was this reply helpful? Yes No
Jinman Microsoft Employee on at

Like (0)

Report

@Bob13 , this is an interesting and valid question.
With many reasons, I would rather go with multiple flows than a big one into certain depths.
I see your concern about viewing activities scattered over multiple flows via process mining though. At the moment, process mining generates a view per flow.

Was this reply helpful? Yes No