Preprocessing error messages

If you encounter any preprocessing errors, review the cause and perform the required action to resolve the error.

If you build a bot that has more than 2,000 lines of code, and if the bot uses descendant actions such as Loop > Continue or Break actions, pre-processing errors can occur. To prevent pre-processing errors, we recommend that you break the larger bot into smaller bots, and run the Task Bot > Run action from any other bot.

Note:
  • From Automation 360 v.23, if an error occurs when you run a bot, a preprocessing or runtime error is shown. Note that preprocessing of child bots does not occur in sequence because these bots are referred in the parent bot and are sometimes in complex nested workflows. Therefore, the errors might be displayed in any sequence for these child bots. The parent bot cannot proceed further until all the errors in the child bots are resolved.
  • The following scenarios are applicable only to Automation 360 v.21 or earlier releases. For v.22, Only the Catch action scenario is applicable, so review the probable cause.
Cause Action required
A mismatch occurred and we did not find the expected variable data type. Use an inline expression or a separate action to convert to the correct variable data type.

Variables overview

A "
quot; is being read as a variable but no such variable exists. 		Use "$" to escape the dollar sign and try again.
The bot is calling another bot, but we did not find the child bot at the specified location. Check the path and try again.
We found a Catch action that is not contained by a Try action. Ensure that each Catch action is contained by a Try action.
We found a Try action that does not contain a Catch action. Each Try action requires at least one Catch action inside it. Ensure that each Try action contains a Catch action.