Migration messages

Migration messages might display at any stage of the migration or Internet Explorer bot conversion. You can review or act on migration messages from these possible sources: Bot Scanner report, Bot Assistant or Bot migration report.

Note:
  • Some messages described on this page do not include a cause or action when the cause is provided as part of the message and do not require any further action.
  • This page also includes Internet Explorer conversion messages that are applicable only for customers impacted by the Internet Explorer end-of-life (EOL) and have chosen to convert IE bots.

Action required messages

These messages in the Bot Scanner report, Bot Migration Wizard, and Migration Assistant after you migrate the bots. You must perform certain actions to successfully run the bots. We recommend that you review the cause and action required to update and run these bots.

Code

A103

Message

For the migrated bot to run, update the Task bot: Run action in the migrated bot by specifying the credential variable for input parameter. A Credential Vault variable cannot be passed in an insecure manner.

Cause The fields in the migrated Enterprise 11 or Enterprise 10 bot display the value as plain text, so to prevent the risk of a security breach in Automation 360, the Credential Vault variable is restricted from passing it in a nonsecure (or insecure) manner.

Unsupported features with workaround

Code

A108

Message

For the migrated bot to run, update the action in the migrated bot by specifying an appropriate Credential Vault Value.

An Automation 360 Credential Vault Value needs to match version 10.x / 11.x Credential Vault value.

Cause

The migrated bot does not have the Credential Vault value assigned to the corresponding action.

Action

To run the migrated bot, create or update the Credential Vault value and assign it to the corresponding action. Ensure that the Credential Vault value in Automation 360 is same as the Enterprise 10 or Enterprise 11 Credential Vault value.
Code

A109

Message

Referenced variables are missing in the V10/11 bot.

For the migrated bot to run, update the corresponding actions in the migrated bot by providing missing required variables.

Cause

Enterprise 11 or Enterprise 10 bot references a non-existent variable in the Variable Operation command.
Action

Either create a variable with the same name and type, or remove the command that references the non-existent variable.
Code

A110

Message

Referenced variables are missing in the V10/11 bot.

For the migrated bot to run, update the IF action in the migrated bot by providing missing required variables.

Cause

The Enterprise 11 or Enterprise 10 bot references a non-existent variable in the If command.
Action

Create a variable with the same name and type, or remove the command that references the non-existent variable.
Code

A111

Message

Referenced variables are missing in the V10/11 bot.

For the migrated bot to run, update the Assign To Clipboard action in the migrated bot by providing missing required variables.

Cause

The Enterprise 11 or Enterprise 10 bot references a non-existent variable in the Assign To Clipboard command.
Action

Update the Assign To Clipboard action with the required missing variable in the migrated bot so that the referenced variables are of the same type.
Code

A112

Message

Referenced variables are missing in the V10/11 bot.

For the migrated bot to run, update the ElseIF action in the migrated bot by providing missing required variables.

Cause

Enterprise 11 or Enterprise 10 bot references a non-existent variable in the ElseIF command.
Action

Either create a variable with the same name and type, or remove the command that references the non-existent variable.
Code

A113

Message

Referenced variables are missing in the V10/11 bot.

For the migrated bot to run, update the Loop action in the migrated bot by providing missing required variables.

Cause

The Enterprise 11 or Enterprise 10 bot references a non-existent variable in the Loop command.
Action

Create a variable with the same name and type, or remove the command that references the non-existent variable.
Code

A116

Message

The MetaBot Logic referenced in the TaskBot is missing. For the migrated bot to run, ensure the referenced MetaBot logic bot is available at the required path in A360. Message code: A116

Cause

The Enterprise 11 or Enterprise 10 bot references a non-existent Taskbot.
Action Ensure that the MetaBot Logic bot exists in Automation 360.
Code

A117

Message

The MetaBot Logic referenced in the parent MetaBot Logic is missing. For the migrated bot to run, ensure the referenced MetaBot Logic bot is available at the required path in A360. Message code: A117

Cause

The Enterprise 11 or Enterprise 10 parent MetaBot Logic references are missing.
Action Ensure that the MetaBot Logic bot exists in Automation 360.
Code

A118

Message

For the migrated bot to run, ensure the child bot is available at the required path.

A child metabot is required for the parent bot to run.

Cause

When migrating a parent bot, if you have not migrated the child bot or you migrated the child bot at a different location.
Action
Verify that you have successfully migrated the child bot. After your verification, perform one of the following actions:
  • Update the link within the parent bot so that it points to the correct location of the migrated child bot.
  • Move the child bot to the same location as the parent bot location.
Code

A119

Message

A referenced DLL file is missing in the V10/11 bot.

For the migrated bot to run, ensure the referenced DLL file is available at the required path.

Cause

When migrating a parent bot, if you have not migrated the DLL file or you migrated the DLL file to a different location, then this issue occurs.
Action
Verify that you have successfully migrated the reference DLL file. After your verification, perform one of the following actions:
  • Update the link within the migrated bot so that it points to the right location of the migrated DLL file.
  • Move the DLL file to the same location as the migrated bot location.
Code

A124

Message

'Play Sound' action has been migrated. File formats .mid, .wma and .avi formats are not supported.

Update the files to .mp3 or .wav format to run the migrated bot.

Code

A125

Message

Credential value of non string type is not supported for DLL Run function in the migrated bot.

For the migrated bot to run, update the "DLL - Run function" with a string type credential variable or a Global value of appropriate variable type and corresponding mapping.

Refer documentation for more details.

Cause

For the DLL Run action, the credential value of only string type is supported. If the credential value is deleted from the DLL Run command in the Enterprise 10 or Enterprise 11 bot, then this issue occurs.
Action

Update the DLL Run action in the migrated bot by specifying the string type credential value and map it to the corresponding parameters in the migrated bot for it to run. If you want to pass a variable type other than string, create a global value of the required variable and map it to the DLL Run action.
Code

A126

Message

Referenced variables are missing in the V10/11 bot.

For the migrated bot to run, update the 'String-BeforeAfter' action in the migrated bot by providing missing required variables.

Cause

In the Enterprise 10 or Enterprise 11 bot, if the referenced variable is deleted from the String-BeforeAfter command, there are no issues. However, after migration, the missing variable causes an issue because the reference variable is required to run the bot in Automation 360.
Action

Because the reference variable is required for the bot to run, create the missing variable and assign it to the String-BeforeAfter action.
Code

A127

Message

Referenced variables are missing in the V10/11 bot.

For the migrated bot to run, update the 'String-Compare' action in the migrated bot by providing missing required variables.

Cause

In the Enterprise 10 or Enterprise 11 bot, if the referenced variable is deleted from the String-Compare command, there are no issues. However, after migration, the missing variable causes an issue because the reference variable is required to run the bot in Automation 360.
Action

Because the reference variable is required for bot to run, create the missing variable and assign it to the String-Compare action.
Code

A128

Message

Referenced variables are missing in the V10/11 bot.

For the migrated bot to run, update the 'String-Find' action in the migrated bot by providing missing required variables.

Cause

In the Enterprise 10 or Enterprise 11 bot, if the referenced variable is deleted from the String-Find command, there are no issues. However, after migration, the missing variable causes an issue because the reference variable is required to run the bot in Automation 360.
Action

Because the reference variable is required for bot to run, create the missing variable and assign it to the String-Find action.
Code

A129

Message

Referenced variables are missing in the V10/11 bot.

For the migrated bot to run, update the 'String-Join' action in the migrated bot by providing missing required variables.

Cause

In the Enterprise 10 or Enterprise 11 bot, if the referenced variable is deleted from the String-Join command, there are no issues. However, after migration, the missing variable causes an issue because the reference variable is required to run the bot in Automation 360.
Action

Because the reference variable is required for bot to run, create the missing variable and assign it to the String-Join action.
Code

A130

Message

Referenced variables are missing in the V10/11 bot.

For the migrated bot to run, update the 'String-Length' action in the migrated bot by providing missing required variables.

Cause

In the Enterprise 10 or Enterprise 11 bot, if the referenced variable is deleted from the String-Length command, there are no issues. However, after migration, the missing variable causes an issue because the reference variable is required to run the bot in Automation 360.
Action

Because the reference variable is required for the bot to run, create the missing variable and assign it to the String-Length action.
Code

A131

Message

Referenced variables are missing in the V10/11 bot.

For the migrated bot to run, update the 'String-Lowercase' action in the migrated bot by providing missing required variables.

Cause

In the Enterprise 10 or Enterprise 11 bot, if the referenced variable is deleted from the String-Lowercase command, there are no issues. However, after migration, the missing variable causes an issue because the reference variable is required to run the bot in Automation 360.
Action

Because the reference variable is required for the bot to run, create the missing variable and assign it to the String-Lowercase action.
Code

A132

Message

Referenced variables are missing in the V10/11 bot.

For the migrated bot to run, update the 'String-Replace' action in the migrated bot by providing missing required variables.

Cause

In the Enterprise 10 or Enterprise 11 bot, if the referenced variable is deleted from the String-Replace command, there are no issues. However, after migration, the missing variable causes an issue because the reference variable is required to run the bot in Automation 360.
Action

Because the reference variable is required for the bot to run, create the missing variable and assign it to the String-Replace action.
Code

A133

Message

Referenced variables are missing in the V10/11 bot.

For the migrated bot to run, update the 'String-Reverse' action in the migrated bot by providing missing required variables.

Cause

In the Enterprise 10 or Enterprise 11 bot, if the referenced variable is deleted from the String-Reverse command,, there are no issues. However, after migration, the missing variable causes an issue because the reference variable is required to run the bot in Automation 360.
Action

Because the reference variable is required for the bot to run, create the missing variable and assign it to the String-Reverse action.
Code

A134

Message

Referenced variables are missing in the V10/11 bot.

For the migrated bot to run, update the 'String-Substring' action in the migrated bot by providing missing required variables.

Cause

In the Enterprise 10 or Enterprise 11 bot, if the referenced variable is deleted from the String-Substring command, there are no issues. However, migration, the missing variable causes an issue because the reference variable is required to run the bot in Automation 360.
Action

Because the reference variable is required for the bot to run, create the missing variable and assign it to the String-Substring action.
Code

A135

Message

Referenced variables are missing in the V10/11 bot.

For the migrated bot to run, update the 'String-Trim' action in the migrated bot by providing missing required variables.

Cause

In the Enterprise 10 or Enterprise 11 bot, if the referenced variable is deleted from the String-Trim command, there are no issues. However, after migration, the missing variable causes an issue because the reference variable is required to run the bot in Automation 360.
Action

Because the reference variable is required for the bot to run, create the missing variable and assign it to the String-Trim action.
Code

A136

Message

Referenced variables are missing in the V10/11 bot.

For the migrated bot to run, update the 'String-Uppercase' action in the migrated bot by providing missing required variables.

Cause

In the Enterprise 10 or Enterprise 11 bot, if the referenced variable is deleted from the String-Uppercase command, there are no issues. However, after migration, the missing variable causes an issue because the reference variable is required to run the bot in Automation 360.
Action

Because the reference variable is required for the bot to run, create the missing variable and assign it to the String-Uppercase action.
Code

A137

Message

A variable is missing in the V10/11 bot.

For the migrated bot to run, update the 'String-BeforeAfter' action in the migrated bot by providing a valid variable.

Cause

The unsupported variable type is assigned to the String-BeforeAfter action in the migrated Enterprise 10 or Enterprise 11 bot.
Action

To run the migrated bot, create a valid string variable type and assign it to the String-BeforeAfter action.
Code

A138

Message

A variable is missing in the V10/11 bot.

For the migrated bot to run, update the 'String-Compare' action in the migrated bot by providing a valid variable.

Cause

The unsupported variable type is assigned to the action in the migrated Enterprise 10 or Enterprise 11 bot.
Action

To run the migrated bot, create a string variable type and assign it to the action.
Code

A139

Message

A variable is missing in the V10/11 bot.

For the migrated bot to run, update the 'String-Find' action in the migrated bot by providing a valid variable.

Cause

The unsupported variable type is assigned to the action in the migrated Enterprise 10 or Enterprise 11 bot.
Action

To run the migrated bot, create a string variable type and assign it to the action.
Code

A140

Message

A variable is missing in the V10/11 bot.

For the migrated bot to run, update the 'String-Join' action in the migrated bot by providing a valid variable.

Cause

The unsupported variable type is assigned to the action in the migrated Enterprise 10 or Enterprise 11 bot.
Action

To run the migrated bot, create a string variable type and assign it to the action.
Code

A141

Message

A variable is missing in the V10/11 bot.

For the migrated bot to run, update the 'String-Length' action in the migrated bot by providing a valid variable.

Cause

The unsupported variable type is assigned to the action in the migrated Enterprise 10 or Enterprise 11 bot.
Action

To run the migrated bot, create a string variable type and assign it to the action.
Code

A142

Message

A variable is missing in the V10/11 bot.

For the migrated bot to run, update the 'String-LowerCase' action in the migrated bot by providing a valid variable.

Cause

The unsupported variable type is assigned to the action in the migrated Enterprise 10 or Enterprise 11 bot.
Action

To run the migrated bot, create a string variable type and assign it to the action.
Code

A143

Message

A variable is missing in the V10/11 bot.

For the migrated bot to run, update the 'String-Replace' action in the migrated bot by providing a valid variable.

Cause

The unsupported variable type is assigned to the action in the migrated Enterprise 10 or Enterprise 11 bot.
Action

To run the migrated bot, create a string variable type and assign it to the action.
Code

A144

Message

A variable is missing in the V10/11 bot.

For the migrated bot to run, update the 'String-Reverse' action in the migrated bot by providing a valid variable.

Cause

The unsupported variable type is assigned to the action in the migrated Enterprise 10 or Enterprise 11 bot.
Action

To run the migrated bot, create a string variable type and assign it to the action.
Code

A145

Message

A variable is missing in the V10/11 bot.

For the migrated bot to run, update the 'String-SubString' action in the migrated bot by providing a valid variable.

Cause

The unsupported variable type is assigned to the action in the migrated Enterprise 10 or Enterprise 11 bot.
Action

To run the migrated bot, create a string variable type and assign it to the action.
Code

A146

Message

A variable is missing in the V10/11 bot.

For the migrated bot to run, update the 'String-Trim' action in the migrated bot by providing a valid variable.

Cause

The unsupported variable type is assigned to the action in the migrated Enterprise 10 or Enterprise 11 bot.
Action

To run the migrated bot, create a valid string variable type and assign it to the action.
Code

A147

Message

A variable is missing in the V10/11 bot.

For the migrated bot to run, update the 'String-UpperCase' action in the migrated bot by providing a valid variable.

Cause

The unsupported variable type is assigned to the action in the migrated Enterprise 10 or Enterprise 11 bot.
Action

To run the migrated bot, create a valid string variable type and assign it to the action.
Code

A149

Message

MetaBot screen that is referenced in the Logic is not present in the MetaBot. For the migrated bot to run, update the object details in the Recorder action. Message code: A149

Cause Screen details are missing in the Recorder package of the migrated bot. These screen details are required in Automation 360.
Action You must manually capture the screen details in the migrated bot for it to run successfully.
Code

A151

Note: As of v.27, bots that contain non-referenced variables are not flagged as Action Required or Review Required in the Bot Scanner utility for the following variables:
  • $Excel Column$
  • $Filedata Column$
  • $Dataset Column$
  • $Table Column$
  • $XML Data Node$
  • $PDFTitle$
  • $PDFSubject$
  • $PDFFileName$
  • $PDFAuthor$
Note: As of v.25, bots that contain non-referenced variables are not flagged as Action Required in the Bot Scanner utility for the following variables:
  • '$Error Description
    #39;
  • '$Error Line Number
    #39;
  • '$FileName
    #39;
  • '$Extension
    #39;
  • $FolderName
    #39;
Messages
  1. '$Error Description
    #39;     variable name has been migrated as '$Error-Description
    #39;    .

    The '$Error Description

    #39; variable used in version 10.x/ 11.x is not created in the A360 due to the absence of actions from corresponding packages.

    For the migrated bot to run, create a variable with the same name '$Error-Description

    #39; or remove the variable from the respective action.

  2. '$Error Line Number
    #39;     variable name has been migrated as '$Error-LineNumber
    #39;    .

    The '$Error Line Number

    #39; variable used in version 10.x/ 11.x is not created in the A360 due to the absence of actions from corresponding packages.

    For the migrated bot to run, create a variable with the same name '$Error-LineNumber

    #39; or remove the variable from the respective action.

  3. '$FileName
    #39;     variable name has been migrated as '$Loop-Files
    #39;         .

    The '$FileName

    #39; variable used in version 10.x/ 11.x is not created in the A360 due to the absence of actions from corresponding packages.

    For the migrated bot to run, create a variable with the same name '$Loop-Files

    #39; or remove the variable from the respective action.

  4. '$Extension
    #39;     variable name has been migrated as '$Loop-Files
    #39;         .

    The '$Extension

    #39; variable used in version 10.x/ 11.x is not created in the A360 due to the absence of actions from corresponding packages.

    For the migrated bot to run, create a variable with the same name '$Loop-Files

    #39; or remove the variable from the respective action.

  5. $FolderName
    #39;     variable name has been migrated as '$Loop-FolderName
    #39;         .

    The '$FolderName

    #39; variable used in version 10.x/ 11.x is not created in the A360 due to the absence of actions from corresponding packages.

    For the migrated bot to run, create a variable with the same name '$Loop-FolderName

    #39; or remove the variable from the respective action.

  6. $PDFAuthor
    #39;     variable name has been migrated as '$PDF-Metadata-Dictionary
    #39;    .

    The '$PDFAuthor

    #39; variable used in version 10.x/ 11.x is not created in the A360 due to the absence of actions from corresponding packages.

    For the migrated bot to run, create a variable with the same name '$PDF-Metadata-Dictionary

    #39; or remove the variable from the respective action.

  7. '$PDFFileName
    #39;     variable name has been migrated as '$PDF-Metadata-Dictionary
    #39;         .

    The '$PDFFileName

    #39; variable used in version 10.x/ 11.x is not created in the A360 due to the absence of actions from corresponding packages.

    For the migrated bot to run, create a variable with the same name '$PDF-Metadata-Dictionary

    #39; or remove the variable from the respective action.

  8. '$PDFSubject
    #39;     variable name has been migrated as '$PDF-Metadata-Dictionary
    #39;    .

    The '$PDFSubject

    #39; variable used in version 10.x/ 11.x is not created in the A360 due to the absence of actions from corresponding packages.

    For the migrated bot to run, create a variable with the same name '$PDF-Metadata-Dictionary

    #39; or remove the variable from the respective action.

  9. '$PDFTitle
    #39;     variable name has been migrated as '$PDF-Metadata-Dictionary
    #39;    .

    The '$PDFTitle

    #39; variable used in version 10.x/ 11.x is not created in the A360 due to the absence of actions from corresponding packages.

    For the migrated bot to run, create a variable with the same name '$PDF-Metadata-Dictionary

    #39; or remove the variable from the respective action.

  10. '$XML Data Node
    #39;     variable name has been migrated as '$Loop-XML-Data-Node
    #39;    .

    The '$XML Data Node

    #39; variable used in version 10.x/ 11.x is not created in the A360 due to the absence of actions from corresponding packages.

    For the migrated bot to run, create a variable with the same name '$Loop-XML-Data-Node
    #39; or remove the variable from the respective action.
  11. '$Excel Column
    #39;     variable name has been migrated as '$Loop-Excel-Column
    #39;    .

    The '$Excel Column

    #39; variable used in version 10.x/ 11.x is not created in the A360 due to the absence of actions from corresponding packages.

    For the migrated bot to run, create a variable with the same name '$Loop-Excel-Column

    #39; or remove the variable from the respective action.

  12. '$Table Column
    #39;     variable name has been migrated as '$Loop-Table-Column
    #39;    .

    The '$Table Column

    #39; variable used in version 10.x/ 11.x is not created in the A360 due to the absence of actions from corresponding packages.

    For the migrated bot to run, create a variable with the same name '$Loop-Table-Column

    #39; or remove the variable from the respective action.

  13. '$WorkItemResult
    #39;     variable name has been migrated as '$workItemResult
    #39;    .

    The '$WorkItemResult

    #39; variable used in version 10.x/ 11.x is not created in the A360 due to the absence of actions from corresponding packages.

    For the migrated bot to run, create a variable with the same name '$workItemResult

    #39; or remove the variable from the respective action.

  14. '$Dataset Column
    #39;     variable name has been migrated as '$Loop-Dataset-Column
    #39;    .

    The '$Dataset Column

    #39; variable used in version 10.x/ 11.x is not created in the A360 due to the absence of actions from corresponding packages.

    For the migrated bot to run, create a variable with the same name '$Loop-Dataset-Column
    #39; or remove the variable from the respective action.
  15. '$Filedata Column
    #39;     variable name has been migrated as '$Loop-Filedata-Column
    #39;    .

    The '$Filedata Column

    #39; variable used in version 10.x/ 11.x is not created in the A360 due to the absence of actions from corresponding packages.

    For the migrated bot to run, create a variable with the same name '$Loop-Filedata-Column

    #39; or remove the variable from the respective action.

Cause (Applies to all A151 messages): This issue occurs if a certain variable is not created in Automation 360 because actions are not present from the corresponding package.
Action (Applies to all A151 messages): You must create a variable of the relevant variable type (string, number, dictionary, and so on) with the same name in Automation 360, or remove the variable from the respective action to run the migrated bot successfully.
Code

A152

Message

This bot has been migrated.

The size of Array type variables exceeds 160,000. Some of the Array type variables are migrated as Table type variables in A360 without the default values.

Default value for the Table type variable may be required for the bot to give same results.

Code

A154

Message

For the migrated bot to run, update the 'Simulate keystrokes' action. The excel paste special behavior in A360 is different from the version 10.x/11.x. Message Code: A154

Cause The Paste Special dialog box varies between Automation 360, Enterprise 11, and Enterprise 10. As a result, the Simulate keystrokes command functions differently.
Action Update the Simulate keystrokes command in the migrated bot.
Code

A155

Message

For the migrated bot to run update the bot name in the Run Task command. The Metabot logic has been migrated by suffixing '-bot' to the file name

Cause When a Logic and a folder in the MetaBot have the same name in Enterprise 11, after migration the name of the Logic name is suffixed with -bot so that the Logic can be migrated.
Action Update the bot name in the Run Task command.
Code

A156

Message

The migrated bot contains DLL action that returns two dimensional arrays of type Single, Int, Int16, Int32, Int64, UInt, UInt16, UInt32, UInt64, Double, Decimal or Boolean and the output of it is mapped to an array type variable.

Update the bot to convert the output array variable (mapped to the return of above listed DLL functions) to String while using it in any operation.

E.g. $arrayoutput[0][0].Number:toString$

$arrayoutput[0][0].Boolean:toString$

Cause When RunDLL output of a function returns 2D array of type number or boolean and is mapped to an array, then Enterprise 11saves those values as string even though they are number or boolean. However in Automation 360 the values are saved as number. Therefore, runtime error is displayed.
Action To run the migrated bot, convert the output array variable that is mapped to the return of DLL functions to string when using it in bot.
Code

A157

Message

For the migrated bot to run, update the source string in the String command.

The variable stored in a text file and assigned to the variable during bot run is not resolving to the expected value. Update the variable directly in the source string without storing it in a text file.
Cause The size of the string variable is greater than 64 kb.
Action Update the variable directly in the source string without storing it in a text file.
Code

A158

Message

Recorder action has been migrated. The object property values greater than 64kb have been truncated. Remove such properties from the object search criteria in the corresponding Recorder action or object condition inside the If or 'Loop While' action in the migrated bot.

Cause The size of the object property value is greater than 64 kb during migration.
Action To ensure that the search criteria works properly for the corresponding Recorder action, update the object property value that is truncated.

Review required messages

These messages are displayed in the Bot Scanner report, Bot Migration Wizard, and Migration Assistant after you migrate the bots. In such cases, the bot is successfully migrated but you still have to manually verify the migrated bots as described in the following messages.

Code

R101

Messages
  1. Excel: Switch to sheet action has been migrated.

    Review the action session name and type to ensure the shared session name is correct.

  2. Excel: Close action has been migrated.

    Review the action session name and type to ensure the shared session name is correct.

  3. Excel: Delete cells action has been migrated.

    Review the action session name and type to ensure the shared session name is correct.

  4. Excel: Find action has been migrated.

    Review the action session name and type to ensure the shared session name is correct.

  5. Excel: Get multiple cells action has been migrated.

    Review the action session name and type to ensure the shared session name is correct.

  6. Excel: Get single cells action has been migrated.

    Review the action session name and type to ensure the shared session name is correct.

  7. Excel: Get cell address action has been migrated.

    Review the action session name and type to ensure the shared session name is correct.

  8. Excel: Get column name action has been migrated.

    Review the action session name and type to ensure the shared session name is correct.

  9. Excel: Get row number action has been migrated.

    Review the action session name and type to ensure the shared session name is correct.

  10. Excel: Replace action has been migrated.

    Review the action session name and type to ensure the shared session name is correct.

  11. Excel: Run macro action has been migrated.

    Review the action session name and type to ensure the shared session name is correct.

  12. Excel: Save workbook action has been migrated.

    Review the action session name and type to ensure the shared session name is correct.

  13. Excel: Set cell action has been migrated.

    Review the action session name and type to ensure the shared session name is correct.

Code

R102

Message

System variable OS Name has been migrated. Review the value returned for the system variable OS Name in the migrated bot.

The value returned by system variable OS Name may be different from version 10.x/11.x.

Code

R103

Message

Object Cloning has been migrated. Review the Image Recognition LeftClick action in the migrated bot.

Migration of Object Cloning configured with play mode Image with action MiddleClick has been migrated with Image Recognition LeftClick action.

Code

R104

Message

String operation - Split action has been migrated. Review the String operation - Split action in the migrated bot.

The Limit field is now divided into 2 fields: All Options and Only. Limit has been migrated to Only since it has a variable.

Code

R105

Message

App Integration action has been migrated. Review the application type Other in the migrated bot.

Migration of App Integration action with application type Other is supported.

Code

R106

Message

OCR action has been migrated. Read the Automation 360 OCR package documentation for details.

ABBYY is the only OCR engine supported.

Cause

Only the ABBYY OCR engine is supported with Automation 360. Irrespective of which OCR engine you have been using in Enterprise 11, after migration your bots will run using only the ABBYY OCR engine.
Action

To learn more about the OCR package, see OCR package.
Code

R107

Message

Email - Connect with Exchange server action has been migrated.

The exchange server version 'Exchange 2013_SP1' is migrated as 'Exchange 2013'. Ensure this version of the Exchange server will work with your system.

Code

R114

Message

Terminal Emulator - Connect action has been migrated.

The connection type is configured as SSH2 since SSH1 is not supported in A360.

No further action required.

Cause

Enterprise 11 and Enterprise 10 support both the SSH1 and SSH2 connection types. Automation 360 is upgraded to support only the SSH2 connection type. However, your migrated bots that were configured with SSH1 will work in Automation 360 and will be configured with the SSH2 connection type by default.
Code

R115

Message

Terminal Emulator - Connect action has been migrated.

All bots now use the Advanced Technology setting. Please test and validate the bot.

Cause

In Enterprise 10 and Enterprise 11, you can choose whether to use the Advanced Technology for the Terminal Emulator - Connect command. Because Automation 360 is upgraded to support only Advanced Technology, all the migrated bots will be configured with Advanced technology for the Terminal Emulator Connect action by default.
Code

R116

Message

The value of the Error Description variable in the migrated bot may be different from version 10.x / 11.x.

Review any action that uses the value of the Error Description variable.

Code

R117

Message

Workload: Insert work item action has been migrated.

The date format needs to be the same in version 10.x / 11.x and Automation 360.

Cause

The date format field in the Workload: Insert work item action uses a default date format.

Action

If the date format is different from the global value AADefaultDateFormat, update the required format in the Workload: Insert work item action.
Code

R118

Message

Assign To Clipboard action has been migrated.

The referenced variable does not exist in version 10.x / 11.x and has been migrated as a string to Automation 360.

The bot may not run as expected.

Code

R119

Message

The Variable Operation action has been migrated.

Variable types do not match. The variable has been disabled in the migrated bot.

No further action required.

Cause

In Enterprise 11 if you change the variable type (for example, from string to dictionary), the bot ignores the change and moves to the next line. However, in Automation 360, the change in the variable is not supported. So if there is a change in variable type in the migrated bot, the variable is disabled to maintain consistent behavior with Enterprise 11.

.
Code

R120

Message

'Wait for Window' action has been migrated. The negative value of the X1 coordinate has been set to 0. No further action required.

Cause

In Enterprise 10 and Enterprise 11, the negative value for the X1 coordinate is supported for the Wait for Window action. In Automation 360, the negative value is not supported, so the negative value of the migrated bot is set to 0 by default.
Code

R121

Message

'Wait for Window' action has been migrated. The negative value of the X2 coordinate has been set to 0. No further action required.

Cause

In the Enterprise 10 and Enterprise 11, the negative value for X2 coordinate was supported for Wait for Window action. In Automation 360, the negative value is not supported, so, negative value of the migrated bot is set to 0 by default.
Code

R122

Message

'Wait for Window' action has been migrated. The negative value of the Y1 coordinate has been set to 0. No further action required.

Cause

In Enterprise 10 and Enterprise 11, the negative value for Y1 coordinate is supported for the Wait for Window action. In Automation 360, the negative value is not supported and so the negative value of the migrated bot is set to 0 by default.
Code

R123

Message

'Wait for Window' action has been migrated. The negative value of the Y2 coordinate has been set to 0. No further action required.

Cause

In Enterprise 10 and Enterprise 11, the negative value for Y2 coordinate is supported for the Wait for Window action. In Automation 360, the negative value is not supported and so the negative value of the migrated bot is set to 0 by default.
Code

R124

Message

'Terminal Emulator' action has been migrated.

Review the action session name to ensure the shared session name is correct.

Code

R126

Message

'Window title regex has been migrated.

Review the Window title regex in the migrated bot if the window is not found during Bot run.

Code

R127

Message

IfImageReco-FileInFile Command has been migrated.

'.jpg, .jpeg, .jpe. .jfif, .bmp, .gif, .png' are the supported file formats for the field 'ImageFile1' action.

Code

R128

Message

Variable with default value greater than 64kb is not supported. The value is stored in a text file and assigned to the variable during bot run.

Code

R129

Message

This bot has been migrated.

For the migrated bot to run, a dictionary variable is required in the input variable mapping of run task action. Review the temp dictionary variable created in the parent and mapped in the input variable.

Code

R130

Message

'Run Task' action has been migrated.

A credential variable is passed to a non-credential type variable in an unsecured manner. For enhanced security pass the credential variable to a credential type variable.

No further action required.

Code

R133

Message

Action with 'AAInstallationPath' has been migrated.

The value of the 'AAInstallationPath' in the migrated bot may be different from version 10.x / 11.x.

Review any action that uses the value of the 'AAInstallationPath' action.

Code

R134

Message

Run Task action has been migrated.

The child bot path in the Run Task action is passed through a variable during run time. The value of the variable should pass the correct path of the child bot during the bot run.

Code

R135

Message

Screen Capture action has been migrated along with Log to file action to capture the image and the error description.

The file path in the Screen capture action is passed through a variable during run time. The file path in the Log to File action is set to $AAApplicationPath$/Temp/Error Handling/ErrorMessage.txt. \

No further action required.

Code

R136

Message Metabot with logic has been migrated.

The same name is used for the Metabot asset folder or logic folder in version 10.x/11.x. The Metabot logic has been migrated by suffixing '-bot' to its name. If any other existing bot matches this new name, the bot will be overridden.

Review the migrated bot.

Code

R137

Message Metabot with logic has been migrated.

This bot has been migrated. The migrated bot has a circular dependency with another bot. Review the bot dependencies in the migrated bot and update the missing dependencies.

Review the migrated bot.

Code

R138

Message This bot has been migrated.

Object property ClickX or ClickY is variablized.

Please recapture the UI object.

Code

R139

Message This bot has been migrated.

Object property SessionId or Id is variablized.

Please recapture the UI object.

Code

R140

Message

The Value of the Error Line Number in the migrated bot may be different from the one in version 10.x/11.x. Review any action that uses the value of the Error Line Number in the migrated bot. Message code:R140

Code

R1004

Message This bot has been migrated.

A variable is used in the 'Host' property of this bot. If the variable is pointing to 'office365.com', this can potentially have an impact on the action since the Basic authentication mode that is used to connect to the email server is deprecated by Microsoft. You are advised to review the variable and update the authentication mode by selecting OAuth 2.0 and configuring the required parameters.

Error messages

These messages are displayed in the Bot Scanner report and Bot Migration Wizard. These messages are displayed when the bot migration is not successful.

Code

E101

Message

This bot cannot be migrated because it has a child bot that uses an unsupported action or system variable.

Cause

A child bot that uses a command that is currently unsupported for migration cannot be migrated. As a result, parent bots that use this child bot also cannot be migrated.
Action

To migrate these parent bots, remove references to the child bot from the parent bot and then migrate that parent bot.

To view unsupported commands that are used in the child bots, go to the list of bots that cannot be migrated and click the child bot name.
Code

E104

Message

This bot cannot be migrated. The Object Cloning command which automates Flash application is not supported in Automation 360. Delete the Object Cloning command which automates Flash application in Enterprise 10.x/Enterprise 11.x bot and then migrate. Message code: E104

Code

E106

Message

This bot cannot be migrated.

The migration of MetaBot with Screens having play mode as Text is not yet supported.

Note: This message is applicable only for Automation 360 v.25 and earlier releases.
Code

E109

Message

This bot cannot be migrated.

The migration of REST API call using SOAP web service with authentication through client certificate is not yet supported.

Code

E110

Message

This bot cannot be migrated.

The migration of OCTET DECIMAL BYTE STRING data type is not yet supported.

Code

E112

Message

This bot cannot be migrated.

The migration of REST API call using SOAP web service action with Outer XML is not yet supported.

Code

E113

Message

This bot cannot be migrated.

The migration of REST API call using SOAP web service action with Inner XML is not yet supported.

Code

E114

Messages
  1. This bot cannot be migrated.

    The migration of VariableOperation - ResetSysVariable action is not yet supported.

  2. This bot cannot be migrated.

    The migration of Internet - IntCon action is not yet supported.

Code

E115

Message

This bot cannot be migrated.

The migration of Variable Operation action resetting system variable $WorkItem$ is not supported.

Resetting the system variable $WorkItem$ is not supported for Variable Operation command.

Use the String > Assign operation and assign an empty string to the $WorkItem$ system variable instead of resetting it.
Code

E116

Message

This bot cannot be migrated.

The migration of Variable Operation action resetting system variable $WorkItemResult$ is not supported.

Cause

Resetting the system variable $WorkItemResult$ is not supported for Variable Operation command.
Action

Use the String > Assign operation and assign an empty string to the $WorkItemResult$ system variable instead of resetting it.
Code

E118

Message

Create the Credential or Locker in Automation 360 before migrating this version 10.x / 11.x bot.

The credential variables for MetaBot-DLL cannot be migrated because the corresponding Credential or Locker is not present in the Control Room.

Cause The associated Credential variable is not migrated for the Metabot-DLL because the associated credential or locker is not present in the Enterprise 11 Control Room.
Action Manually create the credential or locker in the Automation 360 and then migrate the bot.
Code

E119

Message

This bot has an invalid path.

Modify the bot path in version 10.x / 11.x and ensure that the bot runs before migrating.

The path defined in the Run Task action using $AAApplicationPath$ is not in a valid repository folder.

Cause

The Enterprise 11 or Enterprise 10 bot uses an invalid path in the Run Task command of the child bot.
Action

To migrate this bot, modify the Enterprise 11 bot to ensure a valid child bot path is provided after AAApplicationPath.
Code

E120

Message

This bot has an invalid path.

Modify the bot path in version 10.x / 11.x and ensure that the bot runs before migrating.

The path defined in the If - TaskSuccessful action using $AAApplicationPath$ is not in a valid repository folder.

Cause

The Enterprise 11 or Enterprise 10 bot uses an invalid path in the If - TaskSuccessful command of the child bot.
Action

To migrate this bot, modify the Enterprise 11 bot to ensure a valid child bot path is provided after AAApplicationPath.
Code

E121

Message

This bot has an invalid path.

Modify the bot path in version 10.x / 11.x and ensure that the bot runs before migrating.

The path defined in the If - TaskUnsuccessful action using $AAApplicationPath$ is not in a valid repository folder.

Cause

The Enterprise 11 or Enterprise 10 bot uses an invalid path in the If - TaskUnsuccessful command of the child bot.
Action

To migrate this bot, modify the Enterprise 11 bot to ensure a valid child bot path is provided after AAApplicationPath.
Code

E122

Message

This bot has an invalid path.

Modify the bot path in version 10.x / 11.x and ensure that the bot runs before migrating.

The path defined in the ElseIf - TaskUnsuccessful action using $AAApplicationPath$ is not in a valid repository folder.

Cause

The Enterprise 11 or Enterprise 10 bot uses an invalid path in the ElseIf - TaskUnsuccessful command of the child bot.
Action

To migrate this bot, modify the Enterprise 11 bot to ensure a valid child bot path is provided after AAApplicationPath.
Code

E123

Message

This bot has an invalid path.

Modify the bot path in version 10.x / 11.x and ensure that the bot runs before migrating.

The path defined in the ElseIf - TaskSuccessful action using $AAApplicationPath$ is not in a valid repository folder.

Cause

The Enterprise 11 or Enterprise 10 bot uses an invalid path in the ElseIf - TaskSuccessful command of the child bot.
Action

To migrate this bot, modify the Enterprise 11 bot to ensure a valid child bot path is provided after AAApplicationPath.
Code

E124

Message

The value being passed to the DLL function is in an invalid format.

Modify bot in version 10.x / 11.x before migrating.

Validate the array/list variable and the column/index value passed in the DLL function and update the 10.x/11.x bot.

Code

E125

Message

Modify bot in version 10.x / 11.x before migrating.

Update the version 10.x / 11.x bot to include referenced variables for the Assign From Clipboard action. A referenced variable was not found.

Code

E127

Message

Modify bot in version 10.x / 11.x before migrating.

Variable types do not match or have been changed.

Update the variable type in the Variable Operation action in the version 10.x/11.x bot.

Code

E128

Message

This bot cannot be migrated.

The migration of 'MetaBot with Screens' using Silverlight technology is not yet supported.

Code

E129

Message

This bot cannot be migrated.

The migration of 'MetaBot with Screens' captured using Edge browser is not yet supported.

Code

E130

Message

This bot cannot be migrated.

The migration of 'MetaBot with Screens' captured using Firefox browser is not yet supported.

Code

E131

Message

This bot cannot be migrated.

The migration of 'MetaBot with Screens' with the 'GetAllChildrenData' action is not yet supported.

Code

E132

Message

This bot cannot be migrated.

The migration of 'MetaBot with Screens' with the 'GetVisibility' action is not yet supported.

Code

E133

Message

This bot cannot be migrated.

The migration of 'MetaBot with Screens' with linked objects is not yet supported.

Code

E134

Message

This bot cannot be migrated.

The migration of 'MetaBot with Screens' with 'play mode as coordinate for linked objects' is not yet supported.

Code

E135

Message

This bot cannot be migrated.

The migration of 'MetaBot with Screens' with 'play mode as image for linked objects' is not yet supported.

Code

E136

Message

This bot cannot be migrated.

The migration of 'Object Cloning' action with the Edge browser is not yet supported.

This bot cannot be migrated. The Object Cloning command which automates Legacy Edge browser is not supported in Automation 360 . Delete the object cloning command which automates Edge Legacy browser in 10.x/11/x bot and then migrate. Message code: E136

Code

E137

Message

This bot cannot be migrated.

The migration of 'Object Cloning' action with the Firefox browser is not yet supported.

Code

E138

Message

This bot cannot be migrated.

The migration of 'Object Cloning' action with Silverlight is not yet supported.

Code

E139

Message

This bot cannot be migrated.

The migration of 'Object Cloning' action with the 'GetDataofAllchildren' action is not yet supported.

Code

E140

Message

This bot cannot be migrated.

The migration of 'Terminal Emulator - Connect' action with 'Japanese (50939) Codepage' is not yet supported.

Code

E141

Message

This bot cannot be migrated.

The migration of 'Terminal Emulator - Connect action with 'Japanese (51932) Codepage' is not yet supported.

Code

E142

Message

This bot cannot be migrated.

The migration of 'Terminal Emulator - Connect' action with 'Japanese JIS (20932) Codepage' is not yet supported.

Code

E143

Message

This bot cannot be migrated.

The migration of 'Terminal Emulator - Connect' action with 'Japanese JIS (50220) Codepage' is not yet supported.

Code

E144

Message

This bot cannot be migrated.

The migration of 'Terminal Emulator - Connect' action with 'Japanese JIS (50221) Codepage' is not yet supported.

Code

E145

Message

This bot cannot be migrated.

The migration of 'Terminal Emulator - Connect' action with 'Japanese JIS (50222) Codepage' is not yet supported.

Code

E146

Message

This bot cannot be migrated.

The migration of 'Terminal Emulator - Connect' action with 'Japanese Katakana (50930) Codepage' is not yet supported.

Code

E147

Message

This bot cannot be migrated.

The migration of 'Terminal Emulator - Connect' action with 'Japanese Katakana Extended (20290) Codepage' is not yet supported.

Code

E148

Message

This bot cannot be migrated.

The migration of 'Terminal Emulator - Connect' action with 'US-Canada and Japanese (50931)' is not yet supported.

Code

E149

Message

This bot cannot be migrated.

The migration of Walk command with type All is not supported.

Code

E150

Message

This bot cannot be migrated.

The referenced Meta Bot is not available in the provided location. Provide the valid Meta Bot or location in version 10.x / 11.x and try again.

Code

E151

Message

This bot cannot be migrated.

The migration of $IsCognitiveCaptureSuccess$ action is not supported.

Code

E152

Message

This bot cannot be migrated.

Modify the password type variable in version 10.x/11.x bot before migrating.

The migration of command with Password type variable is not supported. This action does not support credential vault variable.

Code

E153

Message

This bot cannot be migrated.

Modify the SMARTWndCtrl action field variable type in version 10.x/11.x bot before migrating.

The migration of SMARTRecorder action SMARTWndCtrl with field 'SetDateRange_NotSupportedAction' of type 'String' is not supported.

Code

E154

Message

This bot cannot be migrated.

The migration of 'MetaBot with Screens' with 'play mode as image for linked objects' and 'play mode as object for main objects' is not yet supported.

Code

E155

Message

This bot cannot be migrated.

The migration of 'MetaBot with Screens' with 'play mode as image for linked objects' and 'play mode as text for main objects' is not yet supported.

Note: This error is fixed in v.30 and later releases.
Code

E156

Message

This bot cannot be migrated.

The migration of 'MetaBot with Screens' with 'play mode as object for linked objects' and 'play mode as image for main objects' is not yet supported.

Code

E157

Message

This bot cannot be migrated.

The migration of 'MetaBot with Screens' with 'play mode as object for linked objects' and 'play mode as coordinate for main objects' is not yet supported.

Code

E158

Message

This bot cannot be migrated.

The migration of 'MetaBot with Screens' with 'play mode as object for linked objects' and 'play mode as text for main objects' is not yet supported.

Code

E159

Message

This bot cannot be migrated.

The migration of 'MetaBot with Screens' with 'play mode as text for linked objects' and 'play mode as object for main objects' is not yet supported.

Code

E160

Message This bot cannot be migrated.

The migration of 'MetaBot with Screens' with 'play mode as text for linked objects' and 'play mode as text for main objects' is not yet supported.

Code

E162

Message This bot cannot be migrated.

The migration of 'MetaBot with Screens' with 'play mode as coordinate for linked objects' and 'play mode as text for main objects' is not yet supported.

Code

E163

Message Network Error: Migration failed due to loss of connectivity between Control Room and Bot Runner machine.
Code

E164

Message

This bot cannot be migrated.

The migration of 'MetaBot with Screens' with 'play mode as text' and having Import Dataset command with action other than GetText, SetText, DoubleClick, LeftClick and RightClick is not yet supported.

Code

E165

Message

This bot cannot be migrated.

The migration of 'MetaBot with Screens' with 'play mode as text' and having any OCR engine other than 'Abbyy' or 'Tesseract' will use 'Abbyy' OCR engine after migration.

Code

E166

Message

This bot cannot be migrated.

The total number of 'If' conditions used in the bot exceed the number of 'If' conditions we currently support.

For the migrated bot to run, split the bot into smaller units and try again.

Code

E167

Message

This bot cannot be migrated.

The total number of 'ElseIf' conditions used in the bot exceed the number of 'ElseIf' conditions we currently support.

For the migrated bot to run, split the bot into smaller units and try again.

Code

E168

Message

This bot cannot be migrated.

The total number of 'Loop' conditions used in the bot exceed the number of 'Loop' conditions we currently support.

For the migrated bot to run, split the bot into smaller units and try again.

Internet Explorer conversion or scanning messages

These messages are displayed in the Bot Scanner report when bots that use Internet Explorer is run or scanned and are not migrated successfully to other supported browsers.

Code

R1001

Message

A variable is used in the 'Location of the program/file' property of this bot. If the variable is pointing to Internet Explorer, update it such that it points to Chromium based Microsoft Edge browser instead. If not, no further action required.

Code

R1002

Message

Browser components such as Menu bar, Status bar, Favorites bar, Command bar and other non-webpage components differ in each browser, and this can potentially have impact on the captured screens in <PACKAGE_NAME - ACTION_NAME>.

You are advised to review and recapture the screen if required.

Code

R1003

Message

RegEx variable used in the window title seems to have partial text corresponding to 'Internet Explorer' hence the title may not get converted as per 'Microsoft Edge' text that is used in the Edge browser window.

You are advised to use 'Internet Explorer' text as a whole in the RegEx variable.

Basic authentication messages

Code

A1001

Message

The Basic authentication mode that is used to connect to the email server is deprecated by Microsoft. For the bot to run, update the authentication mode by selecting OAuth 2.0 and configuring the required parameters. Otherwise, a connection error will occur.

Cause The Basic authentication mode that is used to connect to the email server is deprecated by Microsoft for Exchange Online.
Action For the bot to run, update the authentication mode by selecting OAuth 2.0 and configuring the required parameters.
Code

A1002
Message

The Basic authentication mode that is used to connect to the EWS server is deprecated by Microsoft. For the bot to run, update the authentication mode by selecting OAuth 2.0 and configuring the required parameters. Otherwise, a connection error will occur.

Cause The Basic authentication mode that is used to connect to the email server is deprecated by Microsoft for Exchange Online.
Action For the bot to run, update the authentication mode by selecting OAuth 2.0 and configuring the required parameters.