A developer needs to create a repetitive process in the REFramework. Following the best practices, which action(s) should be performed to defend against potential robot crashes such as "out of memory"?

A developer needs to create a repetitive process in the REFramework. Following the best practices, which action(s) should be performed to defend against potential robot crashes such as "out of memory"?
A . Build a script that compares current CPU usage values to a threshold and clears data as needed.
B . After every transaction, clear the transaction data, close the applications, and re-open the applications.
C . Add a "Clear Collection" activity at the beginning of the Process.xaml workflow.
D . All "Invoke Workflow File" activities from the Main.xaml file should be marked with the Isolated option.

View Answer

Answer: D

Explanation:

The best practice for creating a repetitive process in the REFramework and defending against potential robot crashes such as “out of memory” is to mark all “Invoke Workflow File” activities from the Main.xaml file with the Isolated option. The Isolated option enables the workflow to run in a separate process, which reduces the memory consumption and the risk of memory leaks. It also improves the stability and the performance of the robot, as it isolates the errors and the exceptions that might occur in the invoked workflow. The Isolated option can be found in the Properties panel of the “Invoke Workflow File” activity, under the Options category. By marking all the invoked workflows as Isolated, the developer can ensure that the robot can handle a large number of transactions without crashing or slowing down