Why does try catch skip blocks in production?

Help Studio
, ,
1

I am encountering an issue with the try-catch block in production. As you can see, my program follows a flow where each “block” represents a sequence containing a try-catch block. The intended behavior is that if an exception occurs within any block, the try-catch should handle it, allowing the subsequent block to execute as planned. For instance, if block 3 encounters an exception, block 4 should still proceed. While this works correctly in debug mode, running the robot in production mode causes it to skip all blocks in the diagram upon detecting an exception. The same behavior occurs when using the “continue on exception” function in the Debugging ribbon. Am I missing some configuration that would ensure proper functionality?

This image depicts a flowchart of a process involving file operations and conditional decisions to invoke various workflows and log results. (Captioned by AI)
This image depicts a flowchart of a process involving file operations and conditional decisions to invoke various workflows and log results. (Captioned by AI)996×426 40.4 KB

The image shows a flowchart of a process to handle Excel files, including steps for opening the file, verifying its contents, and logging possible errors. (Captioned by AI)
The image shows a flowchart of a process to handle Excel files, including steps for opening the file, verifying its contents, and logging possible errors. (Captioned by AI)1043×870 30.9 KB

1 Like
2

I discovered that the “continue on exception” button produces the effect, both in debugging mode and in production mode.

The image shows a software development environment interface featuring editing tools and debugging options, with a highlighted tab labeled Depurar. (Captioned by AI)
The image shows a software development environment interface featuring editing tools and debugging options, with a highlighted tab labeled Depurar. (Captioned by AI)807×161 13 KB

In other words, if it remains active in debug mode and is executed (Ctrl + F5), it seems to exhibit the same behavior.

image
image326×215 10 KB

3

Hi @Matias_Clemente.Arg

You can follow some below steps:

Set proper Timeouts on UI activities

Add “Continue On Error” = False

Use Retry Scope if the element might load slowly

Make sure exception type is correctly caught

As well try putting log messages in between and check .
Hope this works for you!

1 Like
5

I can see in your catch block you are using Log Message activity to log variable value. There is possibility that this activity is failing too (could be because of variable is null ?). In catch block log only exception message (exception.message) then check if subsequent blocks are getting executed or not.

1 Like
6

I wonder why it works correctly in “debug” mode but not in “run” mode.

Nonetheless, the issue seems to be related to the “Continue on exception” button, as disabling this button allows it to function properly in both modes.

7

Good day, I wish to inform you that the issue with the exception was evidently caused by a bug. For reasons unknown, it now functions correctly in both ‘Debug’ mode and ‘Execution’ mode.
Nonetheless, I extend my gratitude to @AkshaySandhu and @AkshaySandhu for their responses.

1 Like
8

That’s great!
can you let us know how you resolved it ? like restarted/repair the Studio or you reinstalled Studio/any specific dependency etc.

1 Like
9

I simply restarted my computer. I tend to leave it on for several days, often with the studio open as well… and I noticed that occasionally it glitches.