Fixes
Information on the fixes for IBM® webMethods Integration version 11.2.2 and the subsequent release fixes.
| Issue ID | Release Date | Region | Description |
| BIC-49396 | January 27 2026 |
Europe Frankfurt AWS EU2 West Europe Netherlands Azure EU3 |
Users intermittently encountered an issue where flow services remained locked even after a user session had timed out. When attempting to open a flow service, users repeatedly received an error indicating that another user was editing the flow service and were forced to open it in view-only mode, even when no active editing session existed. Changes have been made to properly handle session timeouts. |
| PIE-100672, PIE-100784 | January 19 2026 |
Australia East Azure AU1 East US Virginia Azure US2 |
Under heavy load, Integration Server could leak JDBC connections from the
connection pool. A leak might also occur if a JDBC connection throws a SQLException
while clearing warnings. This issue is now resolved. |
| January 18 2026 | West Europe Netherlands Azure EU3 | ||
| January 17 2026 |
Asia Pacific Sydney AWS AU2 US West Oregon AWS US1 |
||
| January 10 2026 | Europe Frankfurt AWS EU2 | ||
| BIC-51028 | 16 December 2025 | Europe Frankfurt AWS EU2 | Added support for API tokens when connecting to Bitbucket version control accounts. For more information, see What's new. |
| CCH-9072 | 16 December 2025 | Australia East Azure AU1 | Data retrieved through the Redshift connector failed when NULL Varchar fields appeared as null and decimal fields did not appear in the output. |
| BIC-51071 | 16 December 2025 |
West Europe Netherlands Azure EU3 US West Oregon AWS US1 Europe Frankfurt AWS EU2 East US Virginia Azure US2 Australia East Azure AU1 Asia Pacific Sydney AWS AU2 |
Configured the View Mode warning message to appear only once each time the flow service opens. After the initial display, the warning does not appear again during the same session, preventing repeated alerts and improving the user experience. |
| BIC-50374 | 16 December 2025 |
West Europe Netherlands Azure EU3 US West Oregon AWS US1 Europe Frankfurt AWS EU2 East US Virginia Azure US2 Australia East Azure AU1 Asia Pacific Sydney AWS AU2 |
Fixed an issue where configuring a schedule for flow service execution in Hybrid Integration failed with an Unable to schedule the integration error when users created or modified a recurring daily or weekly schedule. |
| BIC-49372 | 16 December 2025 |
West Europe Netherlands Azure EU3 US West Oregon AWS US1 Europe Frankfurt AWS EU2 East US Virginia Azure US2 Australia East Azure AU1 Asia Pacific Sydney AWS AU2 |
Fixed an issue where Hybrid Integration failed with a validation error when users imported a WSDL file to create a SOAP API. Enhanced file validation now correctly handles WSDL/XML files. |
| BIC-48745 | 16 December 2025 |
West Europe Netherlands Azure EU3 US West Oregon AWS US1 Europe Frankfurt AWS EU2 East US Virginia Azure US2 Australia East Azure AU1 Asia Pacific Sydney AWS AU2 |
Fixed an issue where creating a SOAP API by importing a WSDL file in Hybrid Integration failed with a validation error. Enhanced file validation now correctly handles WSDL/XML files. |
| BIC-49405 | 16 December 2025 |
West Europe Netherlands Azure EU3 US West Oregon AWS US1 Europe Frankfurt AWS EU2 East US Virginia Azure US2 Australia East Azure AU1 Asia Pacific Sydney AWS AU2 |
Fixed an issue where subscribers created for a shared topic with the same name from different projects overrode the existing durable with the same name in the backend. Changed the durable naming format to include the project UID, ensuring subscribers remain differentiated. |
| FLOW-7289, BIC-50192 | 8 December 2025 |
East US Virginia Azure US2 West Europe Netherlands Azure EU3 Australia East Azure AU1 |
Flow service mappings for document references were getting corrupted when flow
services were imported without their associated dependencies. As a result, the mapping definitions
were not preserved correctly after import. This issue is now resolved. Note: For actions related to
this fix, see the Customer Actions section.
|
| 9 December 2025 |
US West Oregon AWS US1 Europe Frankfurt AWS EU2 Asia Pacific Sydney AWS AU2 |
||
| PIE-96632 | 8 December 2025 |
East US Virginia Azure US2 West Europe Netherlands Azure EU3 Australia East Azure AU1 |
The Swagger 2.0 document generated for a REST API Descriptor has HTTP response
codes in the wrong order for some GET endpoints. The document does not maintain the ascending order
of HTTP response codes for some GET endpoints. For example, 404 Not Found appears after
500 Internal Server Error, which creates confusion when reviewing API behavior and
response flows. This issue is now resolved. Note: This fix applies only to new services generated
from the Swagger file.
|
| 9 December 2025 |
US West Oregon AWS US1 Europe Frankfurt AWS EU2 Asia Pacific Sydney AWS AU2 |
||
| BIC-49597, BIC-49657, and BIC-50205 | 8 December 2025 |
East US Virginia Azure US2 West Europe Netherlands Azure EU3 Australia East Azure AU1 |
On the Monitor page, applying filters for flow service executions returned empty results, even when executions existed. Code changes are made to now pass it as * when applying the execution status filter from the user interface. |
| 9 December 2025 |
US West Oregon AWS US1 Europe Frankfurt AWS EU2 Asia Pacific Sydney AWS AU2 |
||
| BIC-48905 | 8 December 2025 |
East US Virginia Azure US2 West Europe Netherlands Azure EU3 Australia East Azure AU1 |
Due to a glitch in the Redis server used by one of our backend components, the listener did not recover during workflow activation, which caused workflow executions to stop. The reconnect logic has now been improved to resolve this issue. |
| 9 December 2025 |
US West Oregon AWS US1 Europe Frankfurt AWS EU2 Asia Pacific Sydney AWS AU2 |
||
| BIC-49880, BIC-49934, BIC-50640, BIC-50870 | 8 December 2025 |
East US Virginia Azure US2 West Europe Netherlands Azure EU3 Australia East Azure AU1 |
Temporary disconnects from the Redis server in the backend runtime caused workflow executions to fail with errors. Code changes have been implemented to handle this issue. |
| 9 December 2025 |
US West Oregon AWS US1 Europe Frankfurt AWS EU2 Asia Pacific Sydney AWS AU2 |
||
| PIE-101910 | 10 November 2025 | Europe Frankfurt AWS EU2 | When High Availability (HA) is enabled for OAuth, if a token is deleted on node1, the change
is not reflected on node2. As a result, when wm.server.oauth:validateAccessToken is called on node2,
it might still return the deleted (purged) token from its in-memory cache. Now when HA is enabled for OAuth, wm.server.oauth:validateAccessToken now checks if an access token is missing from the database but still exists in a node’s in-memory cache. If so, the service automatically removes the related token entries from accessTokenCache, refreshTokenCache, and tokenCache, so that the deleted tokens are no longer returned from the cache. |
| BIC-48799 | 10 November 2025 | Europe Frankfurt AWS EU2 |
In rare cases where execution completes very quickly, the system recorded the end time as one millisecond earlier than the start time. As a result, the user interface continuously displayed an increasing duration, since it calculated the duration using the current time minus the start time when the end time appeared to be earlier. This issue is now fixed. |
| BIC-47471 | 10 November 2025 | US West Oregon AWS US1 | Changes are implemented to retain the previously selected connector accounts during deployment. |
| BIC-48884 | 27 October 2025 | Asia Pacific Sydney AWS AU2 | When creating a REST connector using an external Swagger file or link, the warning message could sometimes become too long and overflow outside the modal window. To resolve this issue, set a maximum height for the modal window so that the content remains contained and scrollable within the modal. |
| 27 October 2025 | Europe Frankfurt AWS EU2 | ||
| 27 October 2025 | US West Oregon AWS US1 | ||
| 28 October 2025 | Australia East Azure AU1 | ||
| 28 October 2025 | West Europe Netherlands Azure EU3 | ||
| 28 October 2025 | East US Virginia Azure US2 | ||
| WFL-8825 | 27 October 2025 | Asia Pacific Sydney AWS AU2 |
When creating a project parameter with the password flag enabled, users were previously able to unset this flag. This allowed them to view parameters that were not created by them. Additionally, passwords in project parameters could be unmasked, making managed passwords visible to project users. This issue has now been resolved. Once a project parameter is created as a password, its type can no longer be changed. This fix applies to both the public API and the user interface. |
| 27 October 2025 | Europe Frankfurt AWS EU2 | ||
| 27 October 2025 | US West Oregon AWS US1 | ||
| 28 October 2025 | Australia East Azure AU1 | ||
| 28 October 2025 | West Europe Netherlands Azure EU3 | ||
| 28 October 2025 | East US Virginia Azure US2 | ||
| FLOW-7294 | 27 October 2025 | Asia Pacific Sydney AWS AU2 |
Previously, global variable substitution occurred only when a project variable was selected in the Set Value component. The latest update resolves this limitation. The system now supports global variable substitution similar to pipeline variable substitution. Users choose whether to substitute global variable values, giving them more flexibility and control. |
| 27 October 2025 | Europe Frankfurt AWS EU2 | ||
| 27 October 2025 | US West Oregon AWS US1 | ||
| 28 October 2025 | Australia East Azure AU1 | ||
| 28 October 2025 | West Europe Netherlands Azure EU3 | ||
| 28 October 2025 | East US Virginia Azure US2 | ||
| BIC-48509 | 27 October 2025 | Asia Pacific Sydney AWS AU2 | When a custom Node.js connector is exported and imported across multiple customer tenants, it retains the same UID. As a result, updates or deletions made in one tenant may not reflect correctly in the intended tenant, leading to inconsistent behavior. This issue is now resolved. |
| 27 October 2025 | Europe Frankfurt AWS EU2 | ||
| 27 October 2025 | US West Oregon AWS US1 | ||
| 28 October 2025 | Australia East Azure AU1 | ||
| 28 October 2025 | West Europe Netherlands Azure EU3 | ||
| 28 October 2025 | East US Virginia Azure US2 | ||
| FLOW-7231 | 27 October 2025 | Asia Pacific Sydney AWS AU2 | In Flow services, branch steps with the Evaluate Labels = true condition previously skipped rendering of steps. The latest update addresses this issue and ensures that all relevant steps render correctly during execution. |
| 27 October 2025 | Europe Frankfurt AWS EU2 | ||
| 27 October 2025 | US West Oregon AWS US1 | ||
| 28 October 2025 | Australia East Azure AU1 | ||
| 28 October 2025 | West Europe Netherlands Azure EU3 | ||
| 28 October 2025 | East US Virginia Azure US2 | ||
| FLOW-7216 | 27 October 2025 | Asia Pacific Sydney AWS AU2 | Custom package Flow services no longer display user information in view mode. This change improves data privacy and aligns with expected visibility settings. |
| 27 October 2025 | Europe Frankfurt AWS EU2 | ||
| 27 October 2025 | US West Oregon AWS US1 | ||
| 28 October 2025 | Australia East Azure AU1 | ||
| 28 October 2025 | West Europe Netherlands Azure EU3 | ||
| 28 October 2025 | East US Virginia Azure US2 | ||
| WFL-8780 | 07 October 2025 | Asia Pacific Sydney AWS AU2 | Resolved an issue where workflow execution failed after reactivating a previously deactivated workflow. This issue was addressed through workflow caching optimizations. |
| 07 October 2025 | East US Virginia Azure US2 | ||
| 09 October 2025 | Europe Frankfurt AWS EU2 | ||
| 09 October 2025 | Australia East Azure AU1 | ||
| 11 October 2025 | West Europe Netherlands Azure EU3 | ||
| 12 October 2025 | US West Oregon AWS US1 |