Known limitations

This topic describes known limitations and provides workarounds if available.

Accessing Decision Intelligence

Feature Limitation Comment or workaround
Tenant session management Users cannot currently log out of a tenant. To end the session, close the browser. This action typically clears session cookies and invalidates the active session.

Managing users

Feature Limitation Comment or workaround
Managing access to a decision automation Only users who are assigned roles directly on a service instance appear in the user list. Users who inherit access through user groups are not currently displayed and cannot be selected for features that require explicit visibility of users. Also, users must have a direct role on the service instance to grant access to other users. Assign a direct role to the user on the service instance to make them visible in the user list.

Managing decisions

Feature Limitation Comment or workaround
Sharing changes When you share a large decision service, an error might occur (HTTP response code 500).

The error is thrown when the operation has not completed on time. Check the Share changes tab after 2 minutes. If changes are still pending, contact IBM support.

To avoid running into this error, try to share your modifications often when you build a large decision service.

Using the Decision Assistant

Feature Limitation Comment or workaround
Using the Build mode
  • You can provide business policies only by copying and pasting text in plain or markup format.
  • The text size limit for business policies is 10,000 characters.
  • The Decision Assistant supports English only.
  • The Decision Assistant generates rules but does not generate decision tables.
 None

Building decision services

Feature Limitation Comment or workaround
Creating business functions Business functions are only available in decision services that have their language set to English. None
Adding the decision logic The following features have limited locale support:
  • Stream operations are not supported in Chinese.
  • String operations are not supported in Chinese, Italian, Portuguese (Brazil), and Japanese.
 If you require support for these features in currently unsupported languages, submit a request for enhancement through the appropriate channels.
Composing and reusing models You cannot reuse task models in decision models. None
Reusing decision artifacts across decision automations You cannot reuse predictive models in other decision automations. Do not publish these models from the Dependencies tab. None
When a decision artifact is reused in a decision automation, deleting the original decision artifact breaks the automation that references it. Always audit dependencies before you delete shared decision artifacts to prevent breaking existing automations.
Reusing decision artifacts across decision services and automations When you reuse a published decision or predictive model that references data types that are already used in the target model, duplicate entries appear in the Output type selection dropdown. This duplication leads to errors, which are displayed in the Error report tab. Remove the duplicated types from the data model used by the target model to resolve the conflict.
Interacting with Decision Designer through an MCP server The MCP server supports English only. None
The MCP server does not support the manipulation of:
  • Task models
  • Predictive models
  • Generative AI models
  • Business functions in data models
  • Function nodes in decision models
 None
Importing industry samples When importing the Banking or the Telecom sample, the import fails and no decisions services are loaded. This issue occurs when the Sample Machine Learning Provider is not available in your tenant.

To resolve this issue:

  1. Create a new decision automation.
  2. Import the sample again.
The import completes successfully and the decision services are loaded correctly.

The Sample Machine Learning Provider has now been created.

Executing decision services

Feature Limitation Comment or workaround
Calling decision services For all the decision runtime REST API endpoints that include exampleInput, when the input of a decision service is too complex, an example is not present in its openapi, and calling the endpoint for generating the example fails with 422 status code. None