Troubleshooting RPA bot generation
This document lists the known issues and the related solutions.
Go through the error messages in the following sections to learn how to resolve the issue.
-
Error messages displayed when you add or edit a custom vendor
-
Error messages that are displayed in the Manage RPA vendors dialog
-
Tagged and Published tasks of an activity does not appear in RPA Script of IBM Task Mining
-
Error messages that are displayed when you generate an RPA bot in IBM Process Mining
-
Viewing the error logs and stacktrace of a custom RPA Bot generator
Error messages displayed when you add or edit a custom vendor
Invalid custom bot generator function name
Error message displayed
Solution
To resolve this issue, you must change the name of the main function in RPA bot generator script to generateBot as shown in the following figure.
For more information on pluggable RPA bot generator script, see Understanding the pluggable RPA bot generator.
Invalid custom bot generator function arguments list
Error message displayed
Solution
To resolve this issue, you must provide three function arguments for the generateBot function as shown in the following figure.
For more information on pluggable RPA bot generator script, see Understanding the pluggable RPA bot generator.
Error messages that are displayed in the Manage RPA vendors dialog
Input contains no snippets for the custom vendor
Error message displayed
Solution
When you upload snippets for a vendor, you must ensure that the RPA vendor name is correctly updated as the value for the vendor field in the JSON file.
For example, if you are adding or updating a custom vendor, redwood, you must update the value of the vendor field in the JSON file as redwood.
Edit and Delete buttons are disabled
Cause
The Edit and the Delete buttons in the Manage RPA vendors dialog are disabled only when the credentials that you are use do not have privileges for editing and deleting custom vendors.
Solution
Do the following steps to edit the tenant permissions:
-
In IBM Process Mining, go to Administration > Authorizations, and then in the left panel, go to Taskminer > RPA Script.
-
In the search box, type the user credentails for which you want to update the permissions, and then click the Edit button corresponding to the credentails.
-
In the Permissions field of the Edit authorization dialog, click write, and then click OK.
For more information, see Overview of the Authorization tab.
Tagged and Published tasks of an activity does not appear in RPA Script of IBM Task Mining
Possible cause
This error can occur if the tagged and published task is marked as human mandatory.
Reason
Since the task is marked as human mandatory, the task cannot be automated. Hence, it is meaningless to display the task in the RPA Script tab for snippets allocation.
Error messages that are displayed when you generate an RPA bot in IBM Process Mining
Error message that is related to bot generation timeout
Error message displayed
Cause
In the tenant-level configuration, you can set a time frame in Pluggable RPA Bot Generator Timeout (seconds) field and define the maximum amount of time the generator script must run. If the script continues to run after the defined duration, then the system automatically stops the process.
Solution 1:
Do the following steps to increase the value defined for timeout:
-
In IBM Process Mining, go to Administration > Tenants, and then click the Edit button corresponding to the tenant for which need to change the value.
-
In the Pluggable RPA Bot Generator Timeout (seconds) field of the Tenant detail tab, type the new time frame, and then click Save.
Solution 2:
You must ensure that the generator script does not have any infinite loops.
Error in creating RPA bot
Error message
Cause
This error occurs when there are issues or defects in the uploaded pluggable RPA bot generator script, for example a syntax error. The error message provides a detailed description and the line numbers in which the defect was observed.
Solution
To resolve this error, you must review the uploaded pluggable RPA bot generator script file to make the necessary changes at the line numbers mentioned in the error message.
For more information, see Viewing the error logs and stacktrace of a custom RPA Bot generator.
BPMN Data model contains no start nodes
Error message
Solution
This error occurs when the BPMN model of the project does not contain a single start node, which is not an ideal case. An ideal BPMN model of the project must have a single start node and one or more final nodes. Hence, to resolve this error, you must verify and update the project configurations.
BPMN data model contains more than one start node
Error message
Solution
This error occurs when the BPMN model of the project contains multiple start nodes, which is not an ideal case. An ideal BPMN model of the project must have a single start node and one or more final nodes. Hence, to resolve this error, you must verify and update the project configurations.
BPMN data model contains no end nodes
Error message
Error Creating RPA Bot for activity name: BPMN data model contains no end nodes. Unable to proceed.
Solution
This error occurs when the BPMN model of the project does not contain a single final node, which is not an ideal case. An ideal BPMN model of the project must have a single start node and one or more final nodes. Hence, to resolve this error, you must verify and update the project configurations.
Bot generation encountered an error
Error message
Error creating RPA bot for Activity Name. Bot generation encountered an error.
Solution
As a first step, you must verify whether any specific reasons are provided in the error message. If no specific reason is displayed in the error message, then you need to verify the server logs to identify the issue. For more information, see Viewing the error logs and stacktrace of a custom RPA Bot generator.
RPA Bot does not open in the vendor application or the completed bot displays errors
Error message
Cause
This error occurs when the generated script includes an incorrect syntax. In most cases, the issue occurs when the necessary imports are missing in the file. The generator expects such imports (if any) to be supplied through the pre-executionScript in the IBM Process Mining application. This error also occurs when the closing scripts that are required for the specific vendor is missing. The closing statements are normally supplied through the post-executionScript in the IBM Process Mining application.
Solution
The following example demonstrates a sample pre-execution script that you could use for UiPath. Note that the required headers for the generated bot are defined in the sample script.
<Activity mc:Ignorable="sap sap2010" x:Class="StateMachine" VisualBasic.Settings="{x:Null}" sap:VirtualizedContainerService.HintSize="1054,1362" sap2010:WorkflowViewState.IdRef="ActivityBuilder_1" xmlns="http://schemas.microsoft.com/netfx/2009/xaml/activities" xmlns:av="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:sap="http://schemas.microsoft.com/netfx/2009/xaml/activities/presentation" xmlns:sap2010="http://schemas.microsoft.com/netfx/2010/xaml/activities/presentation" xmlns:scg="clr-namespace:System.Collections.Generic;assembly=System.Private.CoreLib" xmlns:ucas="clr-namespace:UiPath.Core.Activities.SAP;assembly=UiPath.UiAutomation.Activities" xmlns:ui="http://schemas.uipath.com/workflow/activities" xmlns:uix="http://schemas.uipath.com/workflow/activities/uix" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml">
<TextExpression.NamespacesForImplementation>
<scg:List x:TypeArguments="x:String" Capacity="70">
<x:String>System.Activities</x:String>
<x:String>System.Activities.Statements</x:String>
<x:String>System.Activities.Expressions</x:String>
<x:String>System.Activities.Validation</x:String>
<x:String>System.Activities.XamlIntegration</x:String>
<x:String>Microsoft.VisualBasic</x:String>
<x:String>Microsoft.VisualBasic.Activities</x:String>
<x:String>System</x:String>
<x:String>System.Collections</x:String>
<x:String>System.Collections.Generic</x:String>
<x:String>System.Data</x:String>
<x:String>System.Diagnostics</x:String>
<x:String>System.Drawing</x:String>
<x:String>System.IO</x:String>
<x:String>System.Linq</x:String>
<x:String>System.Net.Mail</x:String>
<x:String>System.Xml</x:String>
<x:String>System.Xml.Linq</x:String>
<x:String>System.Windows.Markup</x:String>
<x:String>UiPath.Core</x:String>
<x:String>UiPath.Core.Activities</x:String>
<x:String>GlobalVariablesNamespace</x:String>
<x:String>GlobalConstantsNamespace</x:String>
<x:String>System.Collections.ObjectModel</x:String>
<x:String>UiPath.Core.Activities.SAP</x:String>
<x:String>System.Security</x:String>
<x:String>UiPath.UIAutomationCore.Contracts</x:String>
<x:String>UiPath.Platform.ObjectLibrary</x:String>
<x:String>System.ComponentModel</x:String>
<x:String>UiPath.UIAutomationNext.Enums</x:String>
<x:String>UiPath.UIAutomationNext.Activities</x:String>
<x:String>UiPath.Shared.Activities</x:String>
<x:String>System.Reflection</x:String>
<x:String>UiPath.Platform.Triggers</x:String>
<x:String>UiPath.Platform.Triggers.Scope</x:String>
<x:String>System.Runtime.Serialization</x:String>
</scg:List>
</TextExpression.NamespacesForImplementation>
<TextExpression.ReferencesForImplementation>
<scg:List x:TypeArguments="AssemblyReference" Capacity="46">
<AssemblyReference>System.Activities</AssemblyReference>
<AssemblyReference>Microsoft.VisualBasic</AssemblyReference>
<AssemblyReference>System.Private.CoreLib</AssemblyReference>
<AssemblyReference>System.Data</AssemblyReference>
<AssemblyReference>System.Data.DataSetExtensions</AssemblyReference>
<AssemblyReference>System</AssemblyReference>
<AssemblyReference>System.Drawing</AssemblyReference>
<AssemblyReference>System.Core</AssemblyReference>
<AssemblyReference>System.Xml</AssemblyReference>
<AssemblyReference>System.Xml.Linq</AssemblyReference>
<AssemblyReference>System.Xaml</AssemblyReference>
<AssemblyReference>UiPath.System.Activities</AssemblyReference>
<AssemblyReference>UiPath.UiAutomation.Activities</AssemblyReference>
<AssemblyReference>UiPath.Studio.Constants</AssemblyReference>
<AssemblyReference>System.ObjectModel</AssemblyReference>
<AssemblyReference>System.Security.Permissions</AssemblyReference>
<AssemblyReference>System.Runtime.InteropServices</AssemblyReference>
<AssemblyReference>UiPath.UIAutomationCore</AssemblyReference>
<AssemblyReference>UiPath.Platform</AssemblyReference>
<AssemblyReference>UiPath.UIAutomationNext</AssemblyReference>
<AssemblyReference>UiPath.UIAutomationNext.Activities</AssemblyReference>
<AssemblyReference>UiPath.Excel.Activities</AssemblyReference>
<AssemblyReference>UiPath.Mail.Activities</AssemblyReference>
<AssemblyReference>UiPath.OCR.Activities</AssemblyReference>
<AssemblyReference>System.ComponentModel.EventBasedAsync</AssemblyReference>
<AssemblyReference>PresentationFramework</AssemblyReference>
<AssemblyReference>System.ComponentModel.TypeConverter</AssemblyReference>
<AssemblyReference>WindowsBase</AssemblyReference>
<AssemblyReference>Microsoft.Win32.Primitives</AssemblyReference>
<AssemblyReference>System.ComponentModel</AssemblyReference>
<AssemblyReference>System.ComponentModel.Primitives</AssemblyReference>
<AssemblyReference>System.Reflection.DispatchProxy</AssemblyReference>
<AssemblyReference>System.Reflection.TypeExtensions</AssemblyReference>
<AssemblyReference>System.Reflection.Metadata</AssemblyReference>
<AssemblyReference>NPOI</AssemblyReference>
<AssemblyReference>System.Memory.Data</AssemblyReference>
<AssemblyReference>System.Console</AssemblyReference>
<AssemblyReference>System.Configuration.ConfigurationManager</AssemblyReference>
<AssemblyReference>System.Memory</AssemblyReference>
<AssemblyReference>System.Private.Uri</AssemblyReference>
<AssemblyReference>UiPath.Workflow</AssemblyReference>
<AssemblyReference>System.Private.ServiceModel</AssemblyReference>
<AssemblyReference>System.Runtime.Serialization.Formatters</AssemblyReference>
<AssemblyReference>System.Private.DataContractSerialization</AssemblyReference>
<AssemblyReference>System.Runtime.Serialization.Primitives</AssemblyReference>
</scg:List>
</TextExpression.ReferencesForImplementation>
You can use the following script as post-execution script for UiPath. You can use this script as the closing tag for the generated script.
</Activity>
Error when you try to view the generated file
Complier Error observed when you open the generated RPA bot in UiPath Studio
Error message
Cause
When you successfully run a custom bot generator and download a bot, it generally means that the Bot is executable in the target environment. One of the scenarios in which the generator execution results in a Bot with compilation errors is when the BPMN of the model contains empty rules. It is an invalid scenario to have rule-based transitions with empty rules. But in this case, the generator might have placed an empty rule within the conditional transition and continued with the generation process.
When this error occurs, you must verify that the process model is valid and that you are generating the bot for valid variants.
Viewing the error logs and stacktrace of a custom RPA Bot generator
If an unexpected error occurs when you run the custom RPA bot generator and a meaningful error is not displayed on the screen, then it is necessary to verify the error logs and stacktrace to accurately identify the issue. For on-premises installations, you can go to the following locations on the Process Mining server to view the files:
-
/opt/processmining/repository/logs/pm-web.log -
/opt/processmining/repository/logs/engine.log
In most cases, these errors occur due to communication issues with task mining service such as invalid configurations and SSL hand-shake issues.