Runtime Release Notes for September 2026

Platform Release

September 12 2026

Runtime features and fixes are not in the runtime release, unless otherwise stated.

New Features

• Cluster Node ID and Execution Worker ID filtering:

  • Added Cluster Node ID and Execution Worker ID filters to the Process Reporting page and the Extended Execution Information panel to help with troubleshooting.

  • Added executionWorkerId and clusterNodeId query filters to the ExecutionRecord API, so you can troubleshoot issues with specific execution workers or cluster nodes.

    (RUN-6895)

Enhancements

• Increased the default Maximum Execution Submissions value for Listen Workers from 10 to 100 to reflect a more realistic use case. (RUN-11553)

• Observability Enhancements

  • Added distributed tracing support for integration processes by capturing and exporting traceparent and tracestate header values per W3C standards, so you can correlate process executions with upstream API requests, including from Boomi's API Gateway. (RUN-10440)

  • Added support for extracting the W3C traceparent header from incoming Shared Web Server requests, linking the caller's trace to the resulting integration process execution for end-to-end distributed tracing. (RUN-11350)

  • Added JVM, operating system, and runtime infrastructure metrics — CPU, memory, filesystem, and file descriptor usage — to the OpenTelemetry plugin, so you can monitor infrastructure health without direct filesystem access. (RUN-11401, RUN-11421, RUN-10443)

  • Added process.name to process log attributes and thread.id to trace attributes, so you can better identify and correlate processes and threads across logs and traces. (RUN-11216)

  • Updated the service name reported to OpenTelemetry — across logs, metrics, and traces — to use the container name instead of the container UUID, so you can more easily identify the corresponding runtime. If this affects your OpenTelemetry dashboards, alerts, or scripts, update them to reference the container name or to use the existing runtime.id attribute. (RUN-11472)

  • Improved trace visibility by adding dedicated span names for each submission handoff point as executions move from head node to execution worker. (RUN-11472)

    Observability enhancements are in the runtime release.

• Java and Docker updates

  • Java updates:

    • Updated runtime cloud installers and upgraders to Java version 11.0.32.9.1, containing the latest security patches.
    • Applied the Java update to Boomi-hosted runtime clouds.

  • Docker Image updates. Visit Dockerhub for more information

    • All V5 images are updated to Java version 11.0.32.9.1.
    • Red Hat image is updated to version 9.8-1786380870, containing the latest security patches.

  • Other updates

    • Extended the security compatibility layer to preserve prior Certificate revocation list (CRL) size limit & and continued trust for certificates chaining to the Chunghwa Telecom root CA on the 2021.01 and 2024.11 compatibility levels after the recent Java upgrade. Integrations on the current default level receive the newer, stricter behavior. (RUN-11473)

    (RUN-10359)

Fixes

• Resolved an issue where the Gateway container log filled with repeated Node is using valid java messages, making meaningful log entries harder to review. (RUN-9487)

• Resolved an issue causing an error message when a runtime shuts down unexpectedly during process execution. (RUN-11184)

• Resolved an issue where calling the ForkedExecutionProperties API with partialUpdate set to true on a new Cloud Cluster or Runtime Cluster cleared default Basic and Advanced property values instead of retaining them. (RUN-11470)

  These fixes are in the runtime release.

• Resolved an issue where redeploying a process after changing its start shape to a non-listener left some listeners in an inconsistent or error state on the Listeners tab. Listeners are now appropriately stopped when the listener shape is changed. (RUN-9330, RUN-8862, RUN-8622)