Known Issues: FNZ Studio 2025

This article provides an overview of Known Issues for released versions of the FNZ Studio 2025 Core Platform and compatible extensions.

Each issue is introduced by a unique code (e.g., KI-2025-1) used only for communication purposes. It has no priority or sorting value.

The article is divided into four parts:

Known Issues in the Core Platform

This section lists all known issues affecting 2025 patch versions. There are currently no Known Issues in the Core Platform.

Known Issues in Extensions

The following list always refers to issues affecting extensions compatible with 2025.x.x patch versions. See the Releases page.

There are currently no Known Issues in Extensions.

Fixed Issues in the Core Platform

Issues Fixed in FNZ Studio 2025 LTS Patch 5 (2025.5.5)

KI-2024-06 - BO Lock Not Released in Chrome/Edge

Under certain circumstances, when a Business Object editor was closed, the corresponding lock was not immediately released. As a result, users might be temporarily unable to commit changes until the lock expired. The issue might appear intermittently and could vary depending on the browser version and configuration. The issue affected users of Chrome and other Chromium-based browsers (e.g. Microsoft Edge).

  • Affected version/s: FNZ Studio 2025.5.4 and lower
  • Workarounds: Chrome users could restore the previous behavior by (please note that Microsoft Edge was expected to be affected by the same browser change):

    • Opening chrome://flags/#deprecate-unload

    • Setting Deprecate unload event to Disabled

    • Restarting the browser

Issues Fixed in FNZ Studio 2025 Patch 2 (2025.5.2)

KI-2025-03 — Potential Missing Data in Distributed Maps (Hazelcast 5.5.0)

Fixed an issue affecting Hazelcast 5.5.0, which might lead to missing data in the distributed maps. The issue only occurred if there were 3 or more nodes started at the same time. The issue is fixed in Hazelcast 5.6.0

  • Affected version/s: Hazelcast 5.5.0 shipped with FNZ Studio 2025 LTS Patch 1
  • Workarounds: There were two possible workarounds:
    • Start the cluster with only 1 or 2 nodes, and join a 3rd node only after the cluster is started.
    • Start the cluster with 3 or more nodes, but use property hazelcast.initial.min.cluster.size to ensure all nodes join the cluster before data loading starts (see also System Upgrade: FNZ Studio 2025).

Issues Fixed in FNZ Studio 2025 Patch 1 (2025.5.1)

KI-2024-05 — Incompatible Inline Actions

Fixed an issue occurring when creating/editing Collection elements in a modal window (i.e. the Create/Edit Element Inline setting in a Data Logic Collection Control is deselected), where Inline Actions (Data Gathering ABC / App Task) did not always match the UI if you selected a different Modal Data Logic in the related setting.

  • Affected version/s: FNZ Studio 2024 LTS Patch 1
  • Workaround: There was no workaround

Fixed Issues in Extensions

There are currently no Fixed Issues in Extensions.