Known Issues in IBM Process Mining 2.2.0

The following sections describe the issues present in IBM Process Mining 2.2.0.

If your legacy project has dots (full stops) "." in the event log's column names, your Analytics queries might have some issues. Replace dots in your CSV header with _.

Make sure that you do not use reserved SQL keywords in your CSV header (such as "select", "count" or "from"), as they might also create issues in the queries.

If you migrate a project that has a process with aliases and no filters, IBM Process Mining might return an unexpected error. To resolve this issue, visualize the process again. To do so, go to Data & Settings > Data > Data source and click Visualize.

This impacts cards and tables widgets with no dimension specified.

When importing a backup, if there is a monitor with a dashboard or filter template that is associated, that association is lost. The user must edit the monitor and re-associate the dashboard or filter template to it.

If you apply an Quick Filter, it does not automatically appear in the Manage Filters tab. The same filter can be applied twice from the Quick Filters and the Manage Filters tab.

Quick Filters are not shareable with other users. You can only share filters from the Manage Filters tab.

If you generate a Task Mining event log with only one task selected, the RPA Candidates tab returns the error No productive time found in task mining project because calculating productive time with only one task is impossible. Select at least two tasks while creating a Task Mining event log.

The RPA Candidates tab in IBM Process Mining functions correctly when you generate an RPA bot for the business activity. However, when you attempt to generate an RPA bot for a different business activity, the following error message is displayed in the RPA Candidates tab: Error in automate Error while retrieving automation status for the project.

When you run a monitor in IBM Process Mining, you might notice the monitor remaining in Running status for a long period without completion.

When the monitor already has a Running status, you cannot run it again. To attempt to run the monitor, do the following steps:

1. From the overflow menu on the monitor, select Duplicate to create a copy of the monitor.
2. Delete the original monitor.
3. Run the duplicate monitor.

In the Simulation results, additional variants might be generated compared to the selected baseline and pathway probability configured in your Simulation scenario.

If you enable Exclude weekends option in the Simulation configuration, the queue is returning incorrect results and incorrect simulation explanations.

While Simulating from BPMN in IBM Process Mining, all gateways are transformed in XOR gateways, since Simulation is only able to manage XOR. Parallelisms in your BPMN model will be transformed in sequences when simulated.