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
After upgrading to 25.0.0-IF006, Navigator logs report an OpenID Connect token validation failure because the JWT issuer (ZEN:<UUID>) does not match the trusted issuer configured in the OpenID Connect client (KNOXSSO)
Symptom:  Authentication failure and failed initialize Workflow authorization.
 
Cause:  In some environments ZEN_INSTANCE_ISS environment variable is set to "true" instead of "false" as it generated in Zen product-configmap for  these zen pods. (usermgmt,zen-core-api & ibm-nginx )
 
Solution: Restart these pods by deleing running pods should resolve the issue.

oc delete pod -l component=usermgmt
oc delete pod -l component=zen-core-api
oc delete pod -l component=ibm-nginx

 
25.0.0-IF006 and future iFixes
Separation of Duty is not supported in the current Fusion recipe implementation.
Symptom: Fusion recipe operations fail or produce unexpected results when Separation of Duty configurations are applied.
 
Cause: Fusion recipe operations fail or produce unexpected behavior when the environment is configured with Separation of Duty policies.
 
Solution: A defect fix is scheduled for delivery in an upcoming maintenance release. No workaround is available at this time.
 
25.0.0-IF005 and future iFixes
Cloud Pak Foundational Services (CPFS), Zen, and Business Teams Service (BTS) do not support external PostgreSQL database configurations when used with Fusion recipes.
Symptom: Fusion Backup and Restore operations for CPFS, Zen, or BTS fail or produce inconsistent results when an external PostgreSQL instance is configured.
 
Cause: The Fusion recipe engine lacks the capability to discover, connect to, or orchestrate externally hosted PostgreSQL instances. Only operator-managed, EDB database instances are supported in the current release.

Solution: A defect fix is scheduled for delivery in an upcoming maintenance release. As an interim measure, avoid configuring CPFS, Zen, or BTS with an external PostgreSQL database when Fusion recipes are in use.
25.0.0-IF005 and future iFixes
Cloud Pak Foundational Services (CPFS) does not support CP4BA deployments that use non-default custom instance namesSymptom: Fusion recipe execution fails when CP4BA is deployed with a custom instance name
 
Cause: The Fusion recipe resolver is hard-coded to the default CP4BA instance naming convention. Non-default instance names are not recognized during runtime resolution, causing the recipe to abort.

Solution: A defect fix is scheduled for delivery in an upcoming maintenance release. As an interim measure, use the default CP4BA instance naming convention for all Fusion-managed deployments.
25.0.0-IF005 and future iFixes
Reconfiguring the database connection to a server with a different port renders the CP4BA application unavailable after a Fusion Backup and Restore operation.Symptom: Following a database server port change, the CP4BA application becomes unreachable and affected pods transition to a non-Running or CrashLoopBackOff state after a Fusion restore.
 
Cause: The Fusion recipe does not propagate port configuration changes to all dependent components at runtime. The stale port value persists in downstream service configurations, resulting in connection failures across the stack after restore

Solution: A defect fix is scheduled for delivery in an upcoming maintenance release. As an interim measure, avoid modifying the database server port post-deployment.
25.0.0-IF005 and future iFixes
CP4BA components configured to use EDB (EnterpriseDB) as their database backend are not supported by the Fusion Backup and Restore recipe in the current release.Symptom: Fusion Backup and Restore operations for CP4BA components using EDB fail or result in an incomplete recovery. Pods relying on EDB-backed services may not return to a Running state following a restore.
 
Cause: The Fusion recipe does not include EDB-aware backup and restore logic. The recipe framework cannot coordinate with the EDB operator to capture or replay database state, resulting in data inconsistency or restore failures.

Solution: A defect fix is scheduled for delivery in an upcoming maintenance release. As an interim measure, avoid deploying CP4BA components with EDB when Fusion Backup and Restore is required.
25.0.0-IF005 and future iFixes
 
 
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
When installing IBM Cloud Pak for Business Automation 25.0.0, you may see the <meta.name>-bas-workplace-job Job will not complete.

Symptom:
The Business Automation Studio Workplace Job Pod fails in creating the Workplace Desktop as it's not able to find the WalkMe Plugin in Navigator.

Starting to create Workplace Desktop

no basic auth

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

100  2855  100  2789  100    66  12073    285 --:--:-- --:--:-- --:--:-- 12359

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

100  3821  100  3821        0  26534      0 --:--:-- --:--:-- --:--:-- 26534

{}&&{"messagesEncoded":true,"sessioninactivelimit":1800,"errors":[{"number":"2807","adminResponse":null,"moreInformation":null,"footer":null,"text":"Invalid plugin ids in the request data: IbmbpmSolutionDiscoveryPlugin,WalkMePlugin.","explanation":"All plugins must be existing in ICN.","userResponse":"Check if all plugins eixst."}]}

Failed creating desktop the 5 times, try again


 

Failed in creating desktop Workplace


Solution:

To resolve this, ensure the following steps are completed:
1. Edit the <meta.name>-initialization-config configmap, and set the nav_walkme_plugin_registered parameter from True to False.

2. Wait 30-45 minutes for the reconcile to complete, eventually the nav_walkme_plugin_registered parameter will be True again.
3. Validate that the <meta.name>-bas-workplace-job has completed on its own.

25.0.0
 


LimitationDescription
Version
25.0.0 IF004 -- WDU is not supported.Symptom: wdu-runtime pod cannot become ready in 25.0.0 IF004.

The WDU Runtime pod may remain in a 0/1 readiness state, and frequently restart. 

Cause: Required endpoint changes introduced in the latest WDU version are not yet reflected in ADP 25.0.0 IF004. 

Solution: Fix to come in future iFix. 
 
25.0.0 IF004
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
 
LimitationDescription
Version
None reported
Symptom:
 

Cause:


Solution:
25.0.0

IBM Business Automation Navigator

LimitationDescription
Version
None reported
Symptom:
 

Cause:


Solution:
25.0.0

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

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
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
LimitationDescription
Version
None reported

Symptom:

Cause:

Solution:

 
25.0.0
 

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
 

IBM Automation Decision Services

LimitationDescription
Version
 
None reported
 
 

Symptom:

Cause:

Solution:

25.0.x
 

IBM Content collector for SAP Applications

LimitationDescription
Version
 
None reported
 

Symptom:

Cause:

Solution:

25.0.0

 

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
 
 

[{"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:
28 July 2026

UID

ibm17183014