Skip to main content

Version 1.18.3.6

Release Date: October 1, 2026 Release Type: Stable Previously published as: 1.18.39 (image tag staging-1.18.39)

Global flow configuration warnings and where-used lists that state which flows a change reaches, where-used checks that are no longer stopped by a single unreadable flow definition, and display fixes in the payload viewer and the Integrations row menu.

Frontend Server​

New Features​

  • Where-used list of flows that define a key locally: GET /api/global-flow-configurations/{configKey}/local-flows lists the flows that carry their own enabled local entry under the same key. It stands next to GET /api/global-flow-configurations/{configKey}/flows, which still lists the flows whose nodes read the key.

Bug Fixes​

  • The in-use warning for global flow configurations describes what a change really reaches: Deleting, disabling or un-applying a global flow configuration is answered with an overridable 409 when flows are involved. An applied-globally definition reaches every flow that has not switched it off, whether or not a node reads it, so the response now states this as a fact (appliedGlobally) instead of listing flows. Flows that define the same key locally keep their own value and are not changed; these are the flows the response now lists, also for a definition that is not applied globally. A delete always asks, a disable asks whenever the definition was enabled, and an un-apply only when it was enabled and applied. A disabled local entry is no longer treated as overriding the global value.
  • One unreadable flow definition no longer blocks operations on other objects: A global flow configuration could not be disabled, taken out of applied-globally or deleted when the stored definition of any single flow could not be read; where-used lists and the usage checks made before an item is deleted were affected in the same way. Such a flow is now skipped, and the skip is written to the server log together with the flow id.

Frontend Web​

New Features​

  • Where Used for global flow configurations shows two lists: The Where Used window now has two tabs: Read in a node, for the flows whose nodes read the key, and Defined locally, for the flows that define the key themselves. If the server cannot provide the second list, the tab says that the list is not available instead of showing an empty table.

Bug Fixes​

  • Configuration In Use window says what the change does: When a configuration is disabled, un-applied or deleted, the window now states the fact, what the action does and then the question. For an applied-globally configuration it says that the configuration reaches every flow and lists nothing; flows that define the same key locally are listed under a sentence saying that they keep their own value. The red error message that repeated the same sentence next to the window is no longer shown.
  • Payload text is no longer hidden under the download and copy buttons: In the node payload drawer the first lines of the payload began underneath the download and copy buttons. The text now starts below the button row.
  • Header and property values stay on screen: In the Headers and Properties tables of the payload drawer, one long key pushed the whole Value column off the right edge, so the names were listed without their values. The two columns now share the available width and long text wraps.
  • The Integrations row menu follows the current deploy state: The flow row menu kept the deploy state it had when the row was loaded. After a deploy or an undeploy it went on offering the wrong action, and a flow that somebody else had already taken down could not be deleted, because Delete Flow kept asking to take it down first. The list is now re-read after a deploy, an undeploy and a refused take-down.

1.18.3.6 is a stable release. Previous: 1.18.3.5