Known issues

Review the known issues in webMethods Integration.

Deploy anywhere flow services fail in new tenants

In newly created tenants, when a user registers a self-managed runtime and attempts to run a deploy anywhere flow service, the following error message is displayed: Account with alias name default/IntegrationLive_Default_Connection@stage00 does not exist.

Workaround: Restart the Cloud Runtime. This is a one-time action that is required only when you run a deploy anywhere flow service for the first time.

Kafka actions and notifications do not clear Afro schemas after switching to a non-Avro serializer or deserializer

When a Kafka action (Produce, Bulk Produce, or Consume) uses Avro key and value schemas, they are stored in the node file. If the connection is later changed to a non-Avro serializer or deserializer (for example, String), the previously saved Avro schemas are retained and cannot be cleared. As a result, the action or notification may fail at run time, even though the configuration appears valid. This issue occurs only when switching from Avro to a non-Avro type.

Workaround: Delete and re-create the Kafka action or notification with the new serializer or deserializer settings.

Array signature issues cause failures in Kafka consumer and bulk produce services

In the Kafka connector, Consumer and Bulk Produce services might fail in certain scenarios due to issues with array signature handling.

Consumer services fail when the input signature explicitly includes offset and partition fields. Bulk Produce services fail in specific cases when headers are used or when an Avro schema is applied. The issue occurs because of incorrect handling of two-dimensional array signatures in the webMethods Integration Service templates.

Note: Bulk Produce services without headers or Avro schema work as expected. Consumer services also function correctly when offset and partition are not included in the input signature.

Public service execution fails to resolve the selected connection for IBM Power

When you execute a public service, the system might fail to resolve the account associated with the IBM Power connection. As a result, the public service execution does not complete successfully, and users may encounter connection resolution errors at run time.

Empty connection account available by default for deploy anywhere flow services

When creating or executing a deploy anywhere flow service for SAP ERP, an account named emptyConnection is available by default in the connection list. Selecting this account for service creation or execution is not supported and will result in errors.

Workaround: Do not select the emptyConnection account. Select a valid, configured connection account instead.