Call "Process.xaml"-Workflow tooks a lot of time

Help Activities
, ,
1

Hi guys,

we use the “UiPath RE Framework” for some of our processes.

In a few processes it tooks a lot of time to call the “Process.xaml” Workflow (>Minute).
Both in the studio and on the RPA client (unattended mode).

Does anyone have any idea what could be the reason for this?

Hardware has 16GB RAM.
UiPath Version 2020.10.0.

Thanks a lot,
Michael

1 Like
2

Is the code in Process.xaml long and complicated?

3

@Michael_Pittner

Sometimes if the process.xaml is large it can take some time…but 1 minute is a little high…try to include a log message before the invoke and as the first activity and see where is it actually taking time

cheers

4

There could be many reason

  1. the workflow contains a lot of activities or complex logic, it will take longer to execute.

  2. If the workflow is interacting with slow applications, such as web applications or legacy systems, it will take longer to execute

  3. Extensive logging or verbose output can slow down execution, especially if writing logs to external systems

To get them rectified

  1. Look for activities that are taking a long time to execute or complex logic that can be simplified. Run in debug mode to understand that

  2. There may be ways to optimize the workflow to make it execute faster. For example, you can try to reduce the number of activities in the workflow
    Try with API calls to interact instead of Ui interaction

  3. Reduce unnecessary logging and consider using log levels appropriately. Avoid verbose logging

  4. If your process involves processing a large amount of data, such as reading and processing thousands of rows in Excel or working with extensive database queries, it can lead to longer execution times. Avoid direct reading of data from any files. Keep them in queues and transactions

Hope this helps

Cheers @Michael_Pittner

5

Hello @Michael_Pittner

There could be several reasons for this issue like :

  1. If your workflow involves heavy computations, large data processing, or frequent interactions with external systems, it can slow down the execution.
  2. If your automation deals with a large volume of data, such as reading or writing extensive Excel files or database operations, it can contribute to slower execution times.
  3. While your hardware has 16GB of RAM, other resource constraints such as CPU usage, disk I/O, or network latency can affect the execution time. Monitor the resource utilization during execution to identify potential bottlenecks.
  4. While your version (2020.10.0) is relatively recent, consider updating to the latest version of UiPath if available, as newer versions often come with performance improvements and bug fixes.
  5. Excessive logging and debugging activities can also slow down the execution.
6

The problem is not the duration time of the process.xaml workflow itself but just the call of the workflow.
Time between last logging before calling the “invoke process workflow”-activity and first logging in the process.xaml workflow is round about 1 minute.

7

I would recommend to try with these rectification

Let us know if u r facing any further challenges

Cheers @Michael_Pittner

8

Hi,

There are several reasons why a workflow might take longer than expected to execute, such as the complexity of the workflow, the number of activities used, and the amount of data being processed1.

use the Invoke Workflow File activity to call your Process.xaml file. This activity is execute a separate workflow file and can help reduce the time it takes to execute your workflow.