Skip to main content

Version 1.18.2.14

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

Flow addresses for polling and subscribing connector types on the Endpoints page, Connector Logs for the inbound side of OFTP2 and X.400, and monitoring log accuracy fixes.

Backend Server​

New Features​

  • Connector Logs cover the inbound side: Steps that a listening connector records before the message enters the flow are now part of the connector trace. Inbound OFTP2 steps are filed under the Start node instead of the End node, and every step of an X.400 poll appears in the trace. Headers, properties and attachments are recorded where the protocol has them, with credentials masked.
  • A connector log failure never fails the message: If recording a connector trace step fails, the message continues to be processed and the original outcome of the run is kept. The first such failure of a run is written to the server log as a warning.

Bug Fixes​

  • OFTP2 runs that end in a negative response are reported as failed: This is a behaviour change. An OFTP2 run that ends with a negative end response (NERP) now fails with the error MIP_OFTP2_NERP, as does a session handshake whose own SSID password cannot be decrypted. Both previously completed as successful.
  • Monitoring log accuracy: A log entry written late by an intermediate node no longer changes a run that has already finished; it is applied only while the run is still in DELIVERING state, on both PostgreSQL and Elasticsearch log storage. The "No Payload" log level is now also honoured when logs are stored in Elasticsearch. The log row of the node that failed now shows the error text as its output payload.

Frontend Server​

New Features​

  • Endpoints page shows a Flow Address for polling and subscribing flows: The Flow Address column was only filled for flows the platform itself hosts (REST, SOAP, Direct, AS2 and XI). It now also shows the remote source the Start node connects to for SFTP, FTP, File, WebDAV, OData, JDBC, REST Polling, OPC UA, JMS, ActiveMQ, RabbitMQ, Solace, Kafka, MQTT, Mail, AWS S3 and SQS, Azure Blob Storage and Storage Queue, Google Pub/Sub, MongoDB, PLC4X and X.400 flows. The address is derived from the deployed flow when the page is read, so already deployed flows show it without a redeploy, flows saved under older connector type names are covered, and credentials are never part of the address.
  • OFTP2 flows show the shared OFTP2 listener address: OFTP2 rows, which used to be blank, now show the address of the platform's shared OFTP2 listener as configured for the installation. When PUBLIC_OFTP2_DISPLAY_URL is set, that value is shown as is.

1.18.2.14 is a stable release. Previous: 1.18.2.13