IBM Support

IBM Cloud Pak for Business Automation 25.0.x Known Limitations

General Page

This web page provides a list of known limitations in IBM Cloud Pak® for Business Automation 25.0.x. Workarounds are provided where possible.

​​IBM Cloud Pak for Business Automation 25.0.x

The following limitations pertain to IBM Cloud Pak for Automation 25.0.x releases. They are subject to change between releases.
 
Additional limitations can be found in the product documentation at Known limitations.
 

Table of contents

 
 
LimitationDescription
Version
During a Fusion backup and restore operation, the backup phase completes successfully, including the execution of the Hook Zen-backup-pod-exec/restore. However, the same hook fails during the restore phase, leading to several key pods failing to transition back to the Running state.
Symptom: 

Restore a. hook zen-backup-pod-exec/restore fails to correctly bring up essential deployments. As a result, the following pods remain in a non-Running state post-restore:

  • ibm-nginx
  • usermgmt
  • zen-core
  • zen-watcher
  • zen-core-api
Solution: 
To manually recover from this issue, run the following command to scale up the impacted pods.
oc scale deploy ibm-nginx usermgmt zen-core zen-watcher zen-core-api --replicas=1
This command restores the expected pod states by explicitly scaling the pods, ensuring the platform services become available again.
 
25.0.0
 

Back to top

 
LimitationDescription
Version
Common Services operator upgrade might become unresponsive when you upgrade from Cloud Pak for Business Automation 24.0.1
Symptom: 
The Common Services operator fails to upgrade and displays the following error message:
Constraints not satisfiable: no operators found from catalog ibm-bts-operator-catalog-v3-35-2 
in namespace production referenced by subscription ibm-bts-operator, subscription ibm-bts-operator exists
This error is intermittent and is not always encountered
Solution: 
Restart the Operator Dependency Lifecycle Manager (ODLM) pod. The Common Services operator upgrade process resumes automatically.
25.0.0
When removing components from your deployment that include IBM Navigator desktops, these desktops are not automatically removed in IBM Cloud Pak for Business Automation 25.0.1

Symptom:
After removing a component, you may still see IBM Business Automation Navigator desktops related to those component(s) when accessing the Admin desktop.  This does not impact application functionality, but these desktops should be cleaned up.

Solution:

Before removing any component which creates a IBM Business Automation Navigator desktop, ensure the following steps are completed:
1. Delete all IBM Business Automation Navigator desktops for the related to the component to be removed.

2. Delete all repository connections in IBM Business Automation Navigator related to the component to be removed.
3. Remove any IBM Business Automation plugins required by the component being removed.
4. Delete the <meta.name>-initilization-config and <meta.name>-verification-config ConfigMaps from your cluster. 

25.0.1

Back to top

 


LimitationDescription
Version
Content Analyzer pods do not support the equals sign (=) character in PostgreSQL database user passwords

Symptom: When you attempt to open or create a Document Processing project, the operation fails if the PostgreSQL database user password contains an equals sign (=) character.

Solution: Use one of the following methods to resolve this issue:

  • Update the PostgreSQL database user password to remove the equals sign (=) character.
  • Configure client-server certificate authentication instead of password authentication.
25.0.1
When you first open an Automation Document Processing (ADP) project, the Share and Version/Deploy buttons do not display on the home screen. This issue does not affect other functionality.Symptom: The Share and Version/Deploy buttons are missing from the home screen when you initially open an ADP project.

Solution: To display the buttons, navigate to another page in the user interface (for example, the Extraction model page), and then return to the home screen. The Share and Version/Deploy buttons then display correctly.		25.0.0
When you configure an IPv6 address for a Db2 database in the Cloud Pak for Business Automation custom resource (CR), Automation Document Processing cannot connect to the database server. You must specify a hostname in the dc_ca_datasource section of the CR.
Symptom: Business Automations for document processing cannot be created when the Cloud Pak for Business Automation configuration uses an IPv6 address for the Db2 database.

Cause: Document processing cannot connect to the Db2 server by using the IPv6 address directly.

Solution: Complete the following steps to configure the Db2 connection:
  1. In the Cloud Pak for Business Automation custom resource, locate the spec.datasource_configuration.dc_ca_datasource section.
  2. Use one of the following methods:
    • If the Db2 server is resolvable by hostname: Specify the hostname in the database_servername property instead of the IPv6 address.
    • If the Db2 server is not resolvable by hostname:
      Specify a placeholder URL-safe name in the database_servername property (for example, db2-ipv6.myhost).
      Specify the IPv6 address in the database_ip property.
  3. Apply the changes to the custom resource.
  4. Wait at least 20 minutes for the operator to apply the changes.

Important: This configuration applies only to the spec.datasource_configuration.dc_ca_datasource section of the custom resource.

 
For example:
datasource_configuration:
  dc_ca_datasource: 
    database_servername: "db2-ipv6.myhost" 
    database_ip: "[2620:1f7:853:a00f:2022:aff:fe16:ca59]"
25.0.0

Back to top

 
LimitationDescription
Version
None reported
Symptom:
 

Cause:


Solution:
25.0.0

Back to top

​IBM Business Automation Navigator

LimitationDescription
Version
None reported
Symptom:
 

Cause:


Solution:
25.0.0

Back to top

 

IBM Business Automation Workflow

LimitationDescription
Version
If the full text search or federation capability is enabled, and the OpenSearch cluster deployed by Cloud Pak foundational services is used as a Federated Data Repository, the  OpenSearch cluster requires a manual configuration.
Symptom: The IBM Business Automation Workflow pod logs contain multiple instances of the following error: 
CWMFS8014I: Index icp4ba-pfs@<index-id> already exists, creation cancelled 
This occurs because automatic index creation is not disabled in OpenSearch (from Cloud Pak foundational services) for indexes related to the Federated Data Repository which contain documents related to tasks, process instances, and case instances.
 
Cause: This issue occurs when the OpenSearch cluster is not configured to prevent automatic index creation. Automatic Elasticsearch and OpenSearch index creation is controlled by the action.auto_create_index setting. By default, this setting is enabled, allowing indexes to be created automatically. When OpenSearch is used as a Federated Data Repository, this setting must be configured to prevent unintended, automatic index creation. For more details about OpenSearch configuration details, see Index settings.
 
Solution: 
To prevent or resolve this issue, disable automatic index creation in the OpenSearch cluster and delete the affected Federated Data Repository indexes. IBM Business Automation Workflow will then automatically recreate the indexes with the correct mappings.
 
To disable automatic index creation, call the PUT _cluster/setting API on the OpenSearch cluster with the following payload:
{
    "persistent":{
        "action.auto_create_index": false
    }
}
 
For instructions on how to retrieve the OpenSearch URL and credentials, see Accessing the OpenSearch cluster REST API.
 
If the issue has already occurred, make sure automatic index creation is disabled and delete the Federated Data Repository index mentioned in the CWMFS8014I error message using the following API call:
DELETE /<index_name>
 
Example:
DELETE /icp4ba-pfs@4a54b8af-a061-40b7-a538-6afb3614962d
 
The index is then automatically recreated by the IBM Business Automation Workflow instance running on containers.
25.0.0

Back to top

 

IBM Business Automation Workflow Process Service

LimitationDescription
Version
If the full text search or federation capability is enabled, and the OpenSearch cluster deployed by Cloud Pak foundational services is used as a Federated Data Repository, the  OpenSearch cluster requires a manual configuration.
Symptom: The IBM Business Automation Workflow Process Service pod logs contain multiple instances of the following error: 
CWMFS8014I: Index icp4ba-pfs@<index-id> already exists, creation cancelled 
This occurs because automatic index creation is not disabled in OpenSearch (from Cloud Pak foundational services) for indexes related to the Federated Data Repository which contain documents related to tasks, process instances, and case instances.
 
Cause: This issue occurs when the OpenSearch cluster is not configured to prevent automatic index creation. Automatic Elasticsearch and OpenSearch index creation is controlled by the action.auto_create_index setting. By default, this setting is enabled, allowing indexes to be created automatically. When OpenSearch is used as a Federated Data Repository, this setting must be configured to prevent unintended, automatic index creation. For more details about OpenSearch configuration details, see Index settings.
 
Solution: 
To prevent or resolve this issue, disable automatic index creation in the OpenSearch cluster and delete the affected Federated Data Repository indexes. IBM Business Automation Workflow Process Service will then automatically recreate the indexes with the correct mappings.
 
To disable automatic index creation, call the PUT _cluster/setting API on the OpenSearch cluster with the following payload:
{
    "persistent":{
        "action.auto_create_index": false
    }
}
 
For instructions on how to retrieve the OpenSearch URL and credentials, see Accessing the OpenSearch cluster REST API.
 
If the issue has already occurred, make sure automatic index creation is disabled and delete the Federated Data Repository index mentioned in the CWMFS8014I error message using the following API call:
DELETE /<index_name>
 
Example:
DELETE /icp4ba-pfs@4a54b8af-a061-40b7-a538-6afb3614962d
 
The index is then automatically recreated by the IBM Business Automation Workflow Process Service instance running on containers.
25.0.0

Back to top

LimitationDescription
Version
When you select Operational Decision Manager (ODM) as a capability in the Red Hat OpenShift Container Platform console, the Cloud Pak for Business Automation deployment cannot pull the required container images from the IBM Container Registry.

Symptom: The ODM pods report ImagePullBackOff and ErrImagePull messages.

Cause: ODM images cannot be successfully pulled from the IBM Container Registry (icr.io).

Solution: Add a pull secret that provides access to cp.icr.io in the CR YAML View in the OCP console. 
The following example shows the ibm-entitlement-key secret in the CP4BA deployment CR:

odm_configuration:
    image:
      pullSecrets:
        - ibm-entitlement-key
 
25.0.0

Back to top

LimitationDescription
Version
None reported

Symptom:

Cause:

Solution:

 
25.0.0

Back to top

 

IBM Automation Workstream Services

LimitationDescription
Version
If the full text search or federation capability is enabled, and the OpenSearch cluster deployed by Cloud Pak foundational services is used as a Federated Data Repository, the  OpenSearch cluster requires a manual configuration.
Symptom: The IBM Automation Workstream Services pod logs contain multiple instances of the following error: 
CWMFS8014I: Index icp4ba-pfs@<index-id> already exists, creation cancelled 
This occurs because automatic index creation is not disabled in OpenSearch (from Cloud Pak foundational services) for indexes related to the Federated Data Repository which contain documents related to tasks, process instances, and case instances.
 
Cause: This issue occurs when the OpenSearch cluster is not configured to prevent automatic index creation. Automatic Elasticsearch and OpenSearch index creation is controlled by the action.auto_create_index setting. By default, this setting is enabled, allowing indexes to be created automatically. When OpenSearch is used as a Federated Data Repository, this setting must be configured to prevent unintended, automatic index creation. For more details about OpenSearch configuration details, see Index settings.
 
Solution: 
To prevent or resolve this issue, disable automatic index creation in the OpenSearch cluster and delete the affected Federated Data Repository indexes. IBM Automation Workstream Services will then automatically recreate the indexes with the correct mappings.
 
To disable automatic index creation, call the PUT _cluster/setting API on the OpenSearch cluster with the following payload:
{
    "persistent":{
        "action.auto_create_index": false
    }
}
 
For instructions on how to retrieve the OpenSearch URL and credentials, see Accessing the OpenSearch cluster REST API.
 
If the issue has already occurred, make sure automatic index creation is disabled and delete the Federated Data Repository index mentioned in the CWMFS8014I error message using the following API call:
DELETE /<index_name>
 
Example:
DELETE /icp4ba-pfs@4a54b8af-a061-40b7-a538-6afb3614962d
 
The index is then automatically recreated by the IBM Automation Workstream Services instance running on containers.
25.0.0

Back to top

 

IBM Automation Decision Services

LimitationDescription
Version
 
None reported
 
 

Symptom:

Cause:

Solution:

25.0.x

Back to top

 

IBM Content collector for SAP Applications

LimitationDescription
Version
 
None reported
 

Symptom:

Cause:

Solution:

25.0.0

Back to top

 

IBM Enterprise Records

LimitationDescription
Version
 
You cannot connect to the IBM Enterprise Records (IER) desktop.
Symptom:
When users try to access the IER desktop, they get the following error:
Cannot connect to the web client
Their logs shows the following exception:
java.lang.NoClassDefFoundError: org.apache.xerces.xni.parser.XMLEntityResolver


Cause:
After IERApplicationPlugin.jar is moved to Java 17, it cannot resolve the path to XercesImpl.jar in the IBM Content Navigator (ICN) container.


Solution:
  1. Download the ier-library.xml file from https://github.com/ibm-ecm/ier-samples.
  2. Put the file into the ICN container in the following path:
    /opt/ibm/wlp/usr/servers/defaultServer/configDropins/overrides
  3. In the same path, create a folder named ier-jars.
  4. Copy and paste xercesImpl.jar from <ier_on-prem_installation>\API\JARM to the ier-jars folder.
  5. Restart the ICN pod and open the IER desktop.
You should now have access to the desktop.
25.0.0

Back to top

 
 

[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBYVB","label":"IBM Cloud Pak for Business Automation"},"ARM Category":[{"code":"a8m0z0000001iUCAAY","label":"Operate-\u003EUMS Install\\Upgrade\\Setup"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"25.0.0;25.0.1"}]

Document Information

Modified date:
11 December 2025

UID

ibm17183014

Page Feedback