Skip to main content
Feedback

Runtime Release Notes for May 2026

Platform Release

May 30 2026

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

New
We added these features

  • Observability enhancements for Cloud Attachments

    • Cloud attachment owners can now configure Runtime Observability settings and stream telemetry data to external monitoring tools. Attachment level observability is separate and runs in parallel to observability settings previously configured for the overall cloud.
    • Attachments can export telemetry data, including metrics, logs, and traces for their attachment’s activity only. This includes telemetry from execution workers and forked executions, but not the overall runtime cloud’s node/container logs.
    • Runtime cloud owners can choose to make this feature available to all or specific attachments in their cloud.
    note

    This feature will be immediately available for private runtime cloud owners, but will be rolled out gradually for Boomi-hosted cloud users, starting with MCS and DCS users.

    (RUN-8800)

  • Forked Execution Properties API

    • Introduced the ForkedExecutionProperties API to programmatically set and manage the forked execution properties of runtime clusters and runtime cloud clusters.
    • Support for the ForkedExecutionProperties API is available in both the Boomi AtomSphere API and Boomi AtomSphere Partner API connectors.
    • Audit log entries are captured for the update operation.
      (RUN-10256)

  • Runtime Management updates

    • Added a description field for the runtimes which can be set via the Atom API or Information page. This allows you to provide additional context for runtimes. (RUN-10786, RUN-10785).
    • Enhanced the Scheduling dialog UI to accurately display selected days for process scheduling, applicable to the Execution and Retry tabs. (RUN-10353)

  • Other enhancements

    • Enhanced the Listener Status in the Platform API so that it returns per-instance (node or execution worker) status details. The UI was also updated to display new degraded status. Runtime owners can enable this feature following the Platform release. (CON-10750)
    • Improved clarity of OpenTelemetry-related log entries in the runtime container, enabling easier troubleshooting and better understanding of the telemetry data collection process. (RUN-10442)
Fix
We fixed these issues

  • Fixed an issue where the parent process execution status was not correctly sent to the platform when a child process timed out, which caused the parent process to remain in a false pending state indefinitely. (RUN-6921)

    This fix is in the Runtime Release.

  • Fixed the time zone discrepancy between the Startup Properties panel and Scheduling dialog, ensuring you see the consistent time zone for your runtime environment. (RUN-10638)

  • Fixed a memory leak in forked executions where child execution IDs were not released after use, causing indefinite accumulation and resulting in high Java heap usage or out-of-memory errors. (RUN-10867)

    This fix is in the Runtime Release.

  • The RuntimeObservabilitySettings update API now validates the logFilterTypes field. Requests containing invalid or duplicate values are rejected with a clear error message, making it easier to identify and fix configuration issues. (RUN-11035, RUN-10964)

  • Fixed the document.id attribute population when multiple document IDs are present, ensuring accurate tracking of combined documents. (RUN-10797)

  • Corrected an issue where execution worker pods were not automatically started when creating a new cloud attachment on an Elastic Cloud, even when the attachment inherited positive Execution Workers and Minimum Execution Workers values from the cloud defaults. (RUN-10725)

  • Corrected the special/extended UTF-8 characters issue with RHEL based images, now allowing you to use special characters in file names and directories. (RUN-10843)