История страницы

Known issues:

Standalone

• The speed of loading properties of an action depends on the level of nesting of that action in the scheme. When interacting with actions with a large number of parameters, you may experience performance issues in the Studio 

• When setting “For All”, additional users may not be able to update information about actions in the studio. In this case, you should manually copy the studio.data file from the folder with the installed studio to the user folder “%LocalAppData%\Robin\Studio” (the path is opened from under the user account) or click the “Reload actions” button in the main menu of the studio.

Release Notes 2.21.1 Enterprise

ROBIN Studio

• There are a number of problems with the actions of the Office group due to recent changes. In particular, if OnlyOffice Document Builder is not installed on the host
• In python actions there may be rare errors with package recovery, in case of a long username
• For the "Keyboard input" action from the "Simulate system" group, the ability to specify a password has been lost, now the action works only for string input.
• A number of errors in python when working with loops may reoccur, details of the problem are being refined
• Confirmed a bug where disabled actions were not saved when the studio cache was updated.It is possible that the information about the host transmitted to the server is incomplete and the agent logs will show the error “Failed to create an instance of SystemUsage”. In this case, launch the file restore.counters.cmd, located in the ROBIN Agent folder, with administrator rights