Skip to main content

Version 1.18.3.1

Release Date: September 28, 2026 Release Type: Stable Previously published as: 1.18.34 (image tag staging-1.18.34)

Global flow configuration follow-up: definitions can optionally be included in an export, deleting a definition cleans up its references in flows, and unblocking a global on a flow is saved correctly.

Backend Server​

Bug Fixes​

  • Groovy editor time limit covers compilation again: The Groovy editor change shipped in 1.18.3.0 has been withdrawn. The editor's 3-second time limit once again covers both compiling and running a script, and the mip.groovy-editor.script-timeout-seconds setting is no longer available. On a heavily loaded server, a script that is slow to compile can therefore be reported as timed out.

Frontend Server​

New Features​

  • Per-flow global configuration overrides are no longer part of the deploy snapshot: A flow's per-flow override (the inherited globals it blocks) is stored only with the flow and is read live by the backend, so saving the flow is all that is needed for a block or unblock to reach the running flow. The unused globalConfigurationOverride column is removed from the deployed_integrations table automatically at startup; no manual migration step is needed. Local flow configuration entries remain deploy-scoped, and an enabled local entry still takes precedence over a global with the same key.
  • Global flow configuration definitions can be included in an export on request: Flow and package export accepts a new option, includeGlobalFlowConfigurations. It is off by default, in which case the bundle carries no global definitions. When it is on, the definitions of every key the flow refers to are exported, including the globals the flow only blocks.

Bug Fixes​

  • Deleting a global definition also removes its references from flows: When a global flow configuration definition is deleted, its key is now removed from every flow's per-flow override. Previously a leftover entry could cause a global created later under the same key to arrive already blocked on those flows.
  • Global definitions in an import bundle are imported through the import window: Definitions carried in a bundle were silently dropped by the analyze-and-apply import that the web console uses. They are now imported there as well: only definitions that do not exist yet are added, an existing definition is never overwritten, and a newly created definition is added disabled and not applied globally, with a warning.

Frontend Web​

New Features​

  • Export options dialog: The Export button on the Integrations page now opens an Export dialog before the bundle is produced. It asks whether to include global flow configuration definitions. The box is unchecked by default and is reset each time the dialog opens, because a definition usually already exists in the target environment with a value that is right for that environment. The flow's local configuration and its per-flow override are part of the flow and are always exported.

Bug Fixes​

  • Unblocking the last blocked global on a flow is saved: In the Configure Flow window, removing the last block from an inherited global was not saved, so the global stayed blocked for that flow. The change is now stored and the global applies to the flow again.

1.18.3.1 is a stable release. Previous: 1.18.3.0