When all branches of a Try step fail, the situation may be logged or reported back to the caller of the robot as an API exception, depending on how the Try step is configured (this is described in detail in How to Handle Errors). When running the robot on RoboServer in versions prior to 8.2, all the details on what caused each branch to fail were logged or reported. However, it was not stated that all branches of the Try step failed, and the name or location of the Try step was not given either (this information was available only in the debugger).

Starting with version 8.2, it will be reported or logged as a separate error that "All alternatives of the Try step failed", including a reference to the Try step. This error will be reported or logged prior to the details about the failed branches. Note that this change may affect some API clients and will affect the contents of the robot property Robot.executionErrors which can be used in expressions in the robot.

If you are using database logging you will have to updated one of the log tables. The ROBOT_MESSAGE in the log database now has an additional column named PROJECTNAME. Before you can use database logging you must update the ROBOT_MESSAGE table. There are two option, either delete the ROBOT_MESSAGE table (you will loose all errors/messages from previous runs), the table will be recreated when RoboServer (or Management Console) is restarted. If you wish to keep history from previous runs, or the credentials used by RoboServer doesn't have the ALTER TABLE privilege you should have your DBA add the PROJECTNAME column. The type of the column should be VARCHAR(255) (NVARCHAR2 on Oracle, NVARCHAR on Sybase and Microsoft SQL server).