Known limitations

Before you use IBM Business Automation Insights, make sure that you are aware of the known limitations.

Table 1. Limitations to IBM Business Automation Insights
Limitation	Description
Alerts	Business Performance Center You cannot create an alert for a period KPI if it contains a group. If you want to create an alert for a period KPI, go to the Monitoring tab and remove the Group by item. Then, go to the Thresholds tab to create one or more alerts.
Business Performance Center	Aggregations Because Business Performance Center uses OpenSearch as its database, approximation problems can be found with aggregations of numbers greater than 2^53 (that is, about 9 * 10^15). See the Limitations section of the Aggregations page of the OpenSearch documentation. Fixed date time range If, in a fixed date time range, you modify only the date or time, your changes are not saved. Data tables When any chart is displayed as a data table, only the first 1000 rows are shown. Data permissions You can set up data permissions by monitoring source or by team. If you encounter an error when you set a permission by source, try setting the same permission by team. Chart window title If the chart window is too small to display the full title, an ellipsis (…) replaces the end of the title. To view the full title, expand the chart window or click the Fullscreen button.
No Business Automation Insights support for IBM Automation Document Processing	The integration between IBM Automation Document Processing (ADP) and Business Automation Insights is not supported. When you deploy or configure the IBM Cloud Pak® for Business Automation platform, select the Business Automation Insights component together with patterns that are supported by Business Automation Insights, such as `workflow` (Business Automation Workflow) or `decisions` (Operational Decision Manager), not just with `document-processing` (IBM Automation Document Processing).
Flink jobs might fail to resume after a crash.	After a Flink job failure or a machine restart, the Flink cluster might not be able to restart the Flink job automatically. For a successful recovery, restart Business Automation Insights. For instructions, see Troubleshooting Apache Flink jobs.
Case event emitter (ICM)	You can configure a connection to only one target object store. The Case event Emitter does not support multiple target object stores.
OpenSearch indices	Defining a high number of fields in an OpenSearch index might lead to a so-called mappings explosion which might cause out-of-memory errors and difficult situations to recover from. The maximum number of fields in OpenSearch indices created by IBM Business Automation Insights is set to 1000. Field and object mappings, and field aliases, count towards this limit. Ensure that the various documents that are stored in OpenSearch indices do not lead to reaching this limit. Event formats are documented in Reference for event emission.
In the BPEL Tasks dashboard, the User tasks currently not completed widget does not display any results.	The search that is used by the widget does not return any results because it uses an incorrect filter for the task state. To avoid this issue, edit the filter in the User tasks currently waiting to be processed search. Set the state filter to accept one of the following values: TASK_CREATED, TASK_STARTED, TASK_CLAIM_CANCELLED, TASK_CLAIMED.
Historical Data Playback REST API	The API plays back data only from closed processes (completed or terminated). Active processes are not handled.
In Case dashboards, elapsed time calculations do not include late events: Average elapsed Time of completed activities and Average elapsed time of completed cases widgets.	Events that are emitted after a case or activity completes are ignored. But by setting the bai_configuration.icm.process_events_after_completion parameter to true, you can set the Case Flink job to process the events that are generated on a case after the case is closed. The start and end times remain unchanged. Therefore, the duration is the same but the properties are updated based on the events that were generated after completion.
Business Automation Insights deployment fails when Apache Kafka is installed in "All namespaces" and Business Automation Insights is deployed in a dedicated namespace.	Kafka monitors Custom Resources (CRs) across all namespaces, including the Business Automation Insights namespace. This causes conflicts when resources such as KafkaUsers or KafkaTopics share the same name across deployments. API requests that rely on short names become ambiguous or fail when both instances are visible from the same namespace. To solve this issue, deploy Apache Kafka in a namespace-scoped mode that does not include the Business Automation Insights namespace.