Hi,
Please consider the following “CLI” launch:
ui.vision.html?macro=TriggerError&closeRPA=1&savelog=hello.txt&storage=xfile
Consider the macro “TriggerError” a macro that intentionally throws an error. If this is a standalone macro the log file hello.txt is indeed generated. However, if TriggerError has a “run TriggerError2” command to call a sub-macro that actually triggers the error, the log file is not generated at all. This means if an error occurs the browser will hang indefinitely until killed through an external tool. closeRPA and closeBrowser are also ignored.
Macros to reproduce the situation:
{
"Name": "TriggerError",
"CreationDate": "2021-3-15",
"Commands": [
{
"Command": "comment",
"Target": "throwError // I'm an error, will UI.Vision RPA close?",
"Value": ""
},
{
"Command": "open",
"Target": "https://example.com/",
"Value": ""
},
{
"Command": "run",
"Target": "TriggerError2",
"Value": ""
}
]
}
{
"Name": "TriggerError2",
"CreationDate": "2021-3-15",
"Commands": [
{
"Command": "store",
"Target": "2",
"Value": "!timeout_wait"
},
{
"Command": "select",
"Target": "xpath=/html/body/div/h1",
"Value": "label=123"
}
]
}