Known limitations

Before you use IBM Business Automation Manager Open Editions, see the known limitations. When possible, workarounds will be included with the limitations.

Table 1. Known limitations

Limitation Description

Limitation	Description
The event subsystem in the BAMOE workflow engine does not have transactional support.	Using transactions that emit events through an emitter like Kafka or CloudEvents in Business Services with Compact Architecture with at least runtime persistence may throw a transaction error with message 'enlisted connection used without active transaction' after starting a process instance.
In a Business Service, Workflows subsystem event related messages are sent even if the process execution fails due to a DB error.	In a process containing a node that sends out a message (for example, Intermediate Message Throw Event), the sending of the message happens when this node is executed. If the execution then encounters an error (for example, coming from the database) and the transaction is rolled back, the message has already been sent.
Native compilation support for workflow projects.	Using certain dependencies (for example, jobs-service-storage-jpa) might cause native builds to fail due to unsupported methods like `Object.wait0`. * You might encounter build-time failures if you attempt to use native compilation with DMN, and DRL projects in version 9.2.0. These problems are fixed in version 9.2.1. * Workflow (BPMN) projects do not support native compilation in version 9.2.0 and 9.2.1.
OpenAPI spec auto-generation when using the io.quarkus:quarkus-oidc extension.	The io.quarkus:quarkus-smallrye-openapi extension will cause errors when starting a Business Service if the io.quarkus:quarkus-oidc extension is also present and no other schema is generated. * This only happens if the io.quarkus:quarkus-oidc extension is enabled. * As a workaround, add the following to your application.properties file: `quarkus.smallrye-openapi.auto-add-bad-request-response=false` * This property will make it so that the "400 Bad Request" outputs are not added to the auto-generated OpenAPI specifications.
Apply an Accelerator in Developer Tools for VS Code fails in Windows.	In the Developer Tools for VS Code, when user tries to apply an Accelerator using Windows, it fails with the message: Error: ENOENT: no such file or directory, unlink '[workspace-root]\.kie-sandbox\accelerator.yaml'. Workaround: User can manually create the folder `.kie-sandbox` in the VS Code workspace folder root with an empty file called `accelerator.yaml`. Then, when the Accelerator is applied, the `accelerator.yaml` will be filled with the proper content.

The event subsystem in the BAMOE workflow engine does not have transactional support.

Using transactions that emit events through an emitter like Kafka or CloudEvents in Business Services with Compact Architecture with at least runtime persistence may throw a transaction error with message 'enlisted connection used without active transaction' after starting a process instance.

In a Business Service, Workflows subsystem event related messages are sent even if the process execution fails due to a DB error.

In a process containing a node that sends out a message (for example, Intermediate Message Throw Event), the sending of the message happens when this node is executed. If the execution then encounters an error (for example, coming from the database) and the transaction is rolled back, the message has already been sent.

Native compilation support for workflow projects.

Using certain dependencies (for example, jobs-service-storage-jpa) might cause native builds to fail due to unsupported methods like Object.wait0.

* You might encounter build-time failures if you attempt to use native compilation with DMN, and DRL projects in version 9.2.0. These problems are fixed in version 9.2.1.

* Workflow (BPMN) projects do not support native compilation in version 9.2.0 and 9.2.1.

OpenAPI spec auto-generation when using the io.quarkus:quarkus-oidc extension.

The io.quarkus:quarkus-smallrye-openapi extension will cause errors when starting a Business Service if the io.quarkus:quarkus-oidc extension is also present and no other schema is generated.

* This only happens if the io.quarkus:quarkus-oidc extension is enabled.

* As a workaround, add the following to your application.properties file: quarkus.smallrye-openapi.auto-add-bad-request-response=false

* This property will make it so that the "400 Bad Request" outputs are not added to the auto-generated OpenAPI specifications.

Apply an Accelerator in Developer Tools for VS Code fails in Windows.

In the Developer Tools for VS Code, when user tries to apply an Accelerator using Windows, it fails with the message:

Error: ENOENT: no such file or directory, unlink '[workspace-root]\.kie-sandbox\accelerator.yaml'.

Workaround: User can manually create the folder .kie-sandbox in the VS Code workspace folder root with an empty file called accelerator.yaml. Then, when the Accelerator is applied, the accelerator.yaml will be filled with the proper content.