When using a securestring variable, the value should never be output in plain text. However, this is exactly what happens if you are using it, have the option to verify that it was typed marked, and something goes wrong. I recommend changing the error output to say what happened to what variable, but not output the value that was contained in the securestring directly to the on-screen output and logfiles.
Hey @robb.franck yes you are right you can’t check the output in logs or plain text .so to handle the you can surround it with try catch to handle the exception.and then that exception you can check in the logs .
cheers
Welcome to the community @robb.franck.
Could you please share more details about the environment, studio & package version to recreate the scenario?
This information would be helpful to the UiPath team to rectify issue.
Hi @robb.franck,
Kindly share the screenshot as well as more details on what type of error causes this?
What does your workflow look like also would help.
Regards
Sonali
Sure. In this automation I am using Studio 24.10.8 and it is working with the Chrome browser. I’m using the ‘Type Into’ activity (UiPath.UIAutomation.Activities 24.10.3) and had marked it to “Verify that userPassword is typed” and it was set to stop on error (userPassword was the variable name that I was using).
When it wasn’t able to verify that the password was typed correctly since it apparently had a problem, it output the value held in the SecureString variable as plain text to the output pane in UiPath. I’m assuming this was also output into the log files.
2 Likes
@loginerror would you be able to recreate this if it’s a bug or not? Thank you 
1 Like
hello, this is a known issue, we will fix it in a future release. thank you.
2 Likes
Thanks @Gabriel_Tatu for the acknowledgement.