Invoke workflow - will this lead to performance issue?

I am breaking my workflows in to smaller work flows and moving reusable code to common workflows and using “invoke workflow” activity to load these workflows. But some people have raised concern about this, because this may lead to performance issue. Is this true ? What is the recommendation / best practice in this regard ? Is there any limit in using invoke workflow ?

What ever you are following is best practice… it is not going to lead any performance issues…

1 Like

Agreed, but I am sure there are some recommendations and best practices from UiPath.

@skini76,Splitting the task into multiple workflows allows you to reuse the file if there are repeated operations you perform on it.
If the same task is done in single workflow then there is no scope for reusability and lines of activitities and code increases which leads to performance issues.

1 Like