Runtime Release Notes for September 2025
- Released Runtime patch 25.09.2, which applies to Boomi Hub public runtime cloud and MCS Hub clouds only. Refer to DataHub's release notes for more information. (HUB-6930)
Native OpenTelemetry Support
For improved monitoring of your integrations at scale, the runtime now includes native support for OpenTelemetry. This lets you send telemetry data from your runtime and integration process executions to third-party application monitoring tools that support the OpenTelemetry standard. As a runtime owner, you can now stream metrics, logs, and traces, in real time, to the monitoring endpoint or OpenTelemetry collector of your choice. You now have a number of basic filters available to manage the telemetry data sent by the runtime. Advanced filtering can be performed within the endpoint application or with a collector.
This feature is available to all accounts and runtime types, with the exception of cloud attachments, including attachments to Boomi hosted runtime clouds. Cloud attachment-specific observability configuration is planned for a future release.
The feature is currently configured via the RuntimeObervabilitySettings platform API. A configuration user interface is planned for a future release.
(RUN-8651, RUN-9741)
To learn more about this feature, refer to Enabling Observability for runtimes
Atom Queues are now Legacy
This release designates Atom Queues as a Legacy feature. This decision reflects our strategic focus on Event Streams, as Boomi’s modern and scalable solution for event-based messaging. As a legacy feature, Atom Queues will remain fully functional and supported for existing accounts. However, Atom Queues will no longer receive enhancements or optimizations, except for critical security fixes, and will not be accessible to new customers.
At this time Atom Queues are not deprecated and there is NO retirement date. You are NOT required to convert your integration processes to use Event Streams.
(RUN-8828)
Refer to this announcement for complete details.
(RUN-8828)
Elastic Executions for Private Runtime Clouds
The new Elastic Executions feature enables runtime clouds deployed to Kubernetes to leverage Kubernetes' native scaling capabilities in order to more effectively manage variable workloads and optimize computing resource utilization. A redesigned execution engine has integration process executions and execution workers run in their own individual Kubernetes pods instead of within the cluster nodes themselves, enabling more granular scaling.
This feature is available to all accounts with private runtime cloud enabled. Note Elastic Executions is only applicable to runtime clouds; it is not applicable to basic runtimes or runtime clusters.
(RUN-7629)
To learn more about this feature, refer to Cloud cluster with elastic scaling in Kubernetes - Overview
Additional runtime cloud management APIs
Following on to the runtime cloud management APIs introduced in the previous release, we’ve added the following new APIs to further help runtime owners manage and automate their clouds:
- AccountCloudAttachmentSummary: Query the list of cloud attachments (from the cloud owner’s account or across child accounts) for one or more runtime clouds. (RUN-7823)
- AccountCloudAttachmentPropertiesDefault: Retrieve and update the default cloud attachment properties for runtime cloud clusters. Updates are captured in the audit log. (RUN-8053)
- Both APIs are available in the AtomSphere API and the AtomSphere Partner API connectors. (RUN-9326, RUN-9179)
To learn more about these new APIs, refer to Account Cloud Attachment Properties Default and Account Cloud Attachment Summary
Java and Docker updates
Java updates:
- Runtime and runtime cloud installers and upgraders are updated to Java version 11.0.28.6.1, containing the latest security patches.
- The Java update is also applied to Boomi-hosted runtime clouds.
(RUN-8224)
Docker Image updates - Published in Dockerhub
- All images are updated to Java version 11.0.28.6.1
- Alpine image is updated to version 3.22.3, containing the latest security patches.
- Red Hat image is updated to version 9.6-1754584681, containing the latest security patches.
- New environment variable
INSTALLATION_DIRECTORYto optionally configure a custom installation directory instead of the default/mnt/boomi.
(RUN-8224)
Additional Atom Queue Cloud Attachment Quotas
Added a number of new cloud attachment quotas to help runtime cloud owners better govern the use of Atom Queues within their clouds. These quotas are added to the Cloud Management > Attachment Quotas screen as well as the existing AccountCloudAttachmentProperties platform API. The Boomi Atom Queue connector is updated to leverage these new quotas.
- Atom Queue Max Batch size: Limit the maximum number of documents in each batch. If this is lower than the connector value, it overrides that value.
- Atom Queue Max Document size: Limits the size of documents sent to the queue
- Atom Queue Commit Batch Limit: Limit the maximum number of document batches to send to the queue per commit
- Atom Queue Message Throttle Rate: Add an intentional delay between messages
- Atom Queue Force File Persistence: Force documents to be persisted on disk instead of memory
(RUN-9395, RUN-9055, RUN-9059, RUN-9092)
- A
NullPointerExceptionno longer occurs when you enable the dynamic connection properties for a connection and set the Dynamic Process Connection property through the Set Properties step in a process. (RUN-5680) - Fixed the broken Learn More links in the Properties panel on the Runtime Management page, enabling users to access related topics on Help Documentation. (RUN-8957)
- Corrected the
NullPointerExceptionerror when getting messages from an empty queue without a timeout, providing you with an empty document response instead of an error. (RUN-8456) - Corrected the issue causing
container.propertiesto become corrupted and prevent cluster recovery after Kubernetes pod failure. (RUN-9358)