Skip to main content

Version 1.18.3.2

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

Deployment status in the designer, undeploy from the designer and the Integrations listing, a guarded two-step delete for deployed flows, and counter delete and where-used fixes.

Frontend Server​

New Features​

  • Deployed flows are protected from accidental deletion: Deleting a deployed flow through the API is now refused with a 409 response that asks for the flow to be undeployed first; previously the delete silently undeployed the flow. Passing undeployIfDeployed on DELETE /api/flows or DELETE /api/flows/{flowId} undeploys the flow first and deletes it only if the undeploy succeeded. In a batch delete only the flows that could not be deleted are reported, and the rest of the batch is still deleted.
  • Deployment status of a flow: GET /api/flows/{flowId}/deployment reports whether a flow is deployed, the deployed version, who deployed it and when, who undeployed it and when (while the flow is down), the flow's current version and last change, and whether the flow has changed since it was deployed. The deployed_integrations table records this in the new deployed_at, deployed_by, undeployed_at and undeployed_by columns. Flow and package listings now also carry each flow's deployed state and deployed version.
  • Counter where-used: GET /api/number-ranges/{id}/flows lists every deployed or saved flow whose Counter node uses the counter, so it is visible which flows keep a counter from being deleted.

Bug Fixes​

  • Where-used lists and in-use checks tolerate flows without a definition: Where-used lists and the in-use checks performed before an item is deleted failed with a server error when a flow without a saved definition existed. Such flows are now skipped, and a deployed flow is no longer reported a second time as a saved one.
  • Sorting a where-used list by flow name works: Sorting a where-used list by one of its listing columns, such as the flow name, returned a server error on every where-used endpoint. The sort fields are now mapped correctly.

Frontend Web​

New Features​

  • Deployment badge in the designer: A DEPLOYED or UNDEPLOYED badge next to the flow name shows whether the flow is live. Hovering over it shows the deployed version and who deployed it and when; for an undeployed flow it shows who took it down and when, followed by what was last live. The hover text also says when saved changes are not live yet or when the viewed version is not the deployed one. While the flow is deployed, a Go to Endpoints link in the hover text opens Operations > Endpoints already filtered to the flow.
  • Undeploy from the designer: A red Undeploy button appears under Deploy while the flow is deployed. It asks for confirmation, and the badge updates once the flow is undeployed, so a flow no longer has to be looked up under Operations > Endpoints to take it down.
  • Undeploy from the Integrations listing: The flow row menu offers Undeploy Flow in the Danger Zone, above Delete Flow. It is shown only for flows that are currently deployed.
  • Deleting a deployed flow is a two-step action: Delete Flow on a deployed flow first opens a Delete Deployed Flow window stating that the flow is deployed and running and that undeploying stops its runtime immediately. On confirmation the flow is undeployed, and only then does the usual delete confirmation appear; answering No there leaves the flow undeployed but not deleted. If the undeploy fails, the delete is not offered. Deleting several selected rows follows the same steps, lists the deployed flows by id, and offers a third answer that deletes only the undeployed flows and leaves the deployed ones running.
  • Where Used for counters: On Operations > Counters, the Where Used Counter action lists the flows whose Counter node uses the counter. The Certificate, OFTP2 and RFC usage windows now use the same where-used window, and sorting it by a column header works.

Bug Fixes​

  • Counters can be deleted from the console: Deleting a counter on the Counters page always failed, whether or not the counter was in use, because the request identified the counter by its name instead of its id; a counter whose name consisted of digits could even cause a different counter to be deleted. Delete now addresses the counter by its id.
  • A partial batch delete is reflected on screen: When only some of the selected flows could be deleted, the deleted rows stayed on screen, still selected, under an open confirmation window until the page was reloaded. The listing is now refreshed, the selection is cleared and the window closes.
  • Flow list in the Configuration In Use window is readable: In the Global Flow Configurations confirmation that names the flows using a configuration, the flow names ran together as one paragraph and ids could be cut in the middle. Each flow is now shown on its own line in a scrolling list.

1.18.3.2 is a stable release. Previous: 1.18.3.1