I’m sorry, but let me clarify something:
The HA recommendations, which involves analyzing the UI by an AI-agent like functionality outside of the server that the automation is running on (I’m assuming it’s outside), and for which Data collection documentation is not available (checked now - still not working), is enabled by default for new process deployments?
If yes:
A. You’re playing with fire from GDPR and general compliance perspective.
B. Have this not been a lesson learned before with the “closest match” selector error messages that were exfiltrating confidential data into the Orchestrator logs?
We all know that whatever we send to Automation Cloud needs to be prescreened, but there was only 1 instance in all the years that I could remember where there was an “unintended leak” of data from Robots into the Orchestrator side - and that was the closest selector error messages (which were capturing whatever the algorithms deemed “close”, which in certain contexts did include things that could not land in the Orchestrator). From our context, when that thing occurred, we were still steering away from the Automation Cloud, and caught it very early, so nothing really happened.
But that would be very far from a short encounter if we were on Automation Cloud back then.
So I’d very kindly ask you to please not enable by default things that make data leave robot servers. We do not need more rounds with compliance teams than we already have.
And yes - our OPS did catch that it’s enabled by default when doing a deploy today (that’s why I’m posting here), and nothing actually happened, but it was a bit too close for comfort.
As a sidenote - your documentation on how to disallow Healing Agent on organization level is either confusing, or I’m just dumb with Automation Ops. Probably the latter, but for silly old folks like me (or people who haven’t really used Automation Ops before [also partially me]) it would be nice to have a very clear “put this here” step by step, especially since it’s on by default and we have to block it. A global “Healing Agent On/Off” would be nice, but I guess instead we need to scramble around in different places and hope that it’s enough and we didn’t miss something.