Empty Locals panel in Debug mode after Find Children Activity

[codemonkee (Tim)]

I have a very simple sequence Find Image > Find Children > Log Message
When in debug mode the locals panel populates for a few of the activities, but clears out on the last one after the Find Children.

Commenting out the Find Children activity and debugging the sequence, the Locals panel will populate at the break point placed on the the Log Message activity.

Studio 2019.10.4 - 2/6/2020
Enterprise License
Windows Installer

Microsoft Windows 10 Enterprise 64-bit
.NET Framework Version 4.7.2 or later

Packages:
UiPath.Systems.Activities 19.10.1
UiPath.UIAutomation.Activities 19.11.2

A couple similar reports

Empty Locals Panel in Debug Mode

Scenario: In debug mode, when I set a breakpoint within an invoked workflow, I am frequently unable to see the values of any local variables set within that workflow. Steps to reproduce: Create a process, invoke a workflow with local variables inside it. Place a break point somewhere within the workflow. Run debug mode from the top/main process level. This is not easy to reproduce since it is intermittent. Lately I’ve been getting it all the time though. Current Behavior: Locals panel in debu…

Local Variables panel empty in Debug mode

Local Variable panel is empty on Debug Mode For first two invoke workflow able to view the variables on the third workflow not able view the local variable. please help

Locals Panel empty

Hi, I recently encountered a problem whenever I run in debug mode: [image] I’m in debug mode and yet it does not show any variables or arguments. Any solution to this is very much appreciated. Thanks

[loginerror (Maciej Kuźmicz)]

Thanks for the report, I registered it in our issue tracker.

For the record, I couldn’t reproduce it on latest Community Edition with your activity packages verions (System and UiAutomation), but our team will have a look.

Please try updating activity packs just as a test.

[loginerror (Maciej Kuźmicz)]

An update. The bug was investigated, but we were no longer able to reproduce it on Studio 20.10.2.

Let us know if it is still occurring for you, but otherwise I think we can call it resolved.