onError #restart jumps to the line just after Run (submacro), not top of the main macro

UI.Vision RPA Bug Reports
1

on my browser,
onError #restart jumps to the line just after Run (submacro), not top of the main macro.
is this a bug and not intended?

main macro:

{
“Name”: “999_test_001”,
“CreationDate”: “2020-5-27”,
“Commands”: [
{
“Command”: “onError”,
“Target”: “#restart”,
“Value”: “”
},
{
“Command”: “store”,
“Target”: “false”,
“Value”: “!ErrorIgnore”
},
{
“Command”: “echo”,
“Target”: “this is 999_test_001”,
“Value”: “”
},
{
“Command”: “run”,
“Target”: “999_test_002”,
“Value”: “”
},
{
“Command”: “echo”,
“Target”: “back to 999_test_001”,
“Value”: “”
},
{
“Command”: “throwError”,
“Target”: “throw error”,
“Value”: “”
}
]
}

sub macro:

{
“Name”: “999_test_002”,
“CreationDate”: “2020-5-27”,
“Commands”: [
{
“Command”: “echo”,
“Target”: “this is sub macro”,
“Value”: “”
},
{
“Command”: “onError”,
“Target”: “#restart”,
“Value”: “”
},
{
“Command”: “store”,
“Target”: “false”,
“Value”: “!ErrorIgnore”
}
]
}

tested on:
Chrome extension v.5.5.7
Windows 10

thank you

2

I confirmed this issue. We will fix it soon.

3

Fixed in today’s V5.7.5 release.

4

Now, I have a different kind of error…
If we define onError #restart in the parent macro, if error occurs in the sub-macro, sub-macro is restarted, not the main macro.

It would be nice if labels from parent macro(s) are visible inside sub-macro(s), so we could use onError #goto label_somewhere_in_the_parent-tree or…

… if sub-macros could be aware of the parent macros, so we could use something like onError #restart some_macro_in_the_parent_tree.

5

My setup:
UI.Vision RPA 5.8.8
Google Chrome version 86.0.4240.111 (Official Build) (64-bit)
Windows 10 Pro 64-bit
Intel Core i5-6300U
16GB RAM

As I said in my previous post, we still have this bug, so admin please re-open this issue. Using run() with this issue is pointless, because when error occur inside sub-macro, you will be stuck inside sub-macro. There are some workarounds, but more elegant solution would be that onError works as advertised.

Also, I would like to add that if we use main macro in the “Play Loop” and error occurs inside sub-macro, main macro will not continue with the next loop, even if “If error happens in loops: -Continue next loop” options is selected.