We encountered a similar issue post-launch where control didn’t return to BP and it kept getting stuck and showing a warning state for a prolonged period until someone forced a restart of the machine.
It seems this launch-related problem still persists in the newer V7 versions, as users continue to report it.
A few other team members have also observed the same. We had raised this with the Support team last year and did a lot of R&D and time spent on this, but nothing helped permanently fix it, so with respect of time, we had to proceed with a workaround.
But definitely I agree, this is something critical that needs to be immediately fixed, as the UI automation is a core part of the automation.
