Version 1.18.2.15

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

Outbound AS2 over HTTPS with an optional partner TLS certificate, and a flow-level monitoring dashboard with backend alert rules.

Outbound AS2 over HTTPS: The outbound AS2 connector can now send to partner endpoints that accept only TLS. A flow selects the scheme (HTTP or HTTPS) and, optionally, a certificate from the platform certificate store to trust for the partner's server; without one, the default trust store of the runtime is used. Existing flows keep sending over plain HTTP unchanged. Hostname verification is always on, and a selected certificate that cannot be loaded fails the send instead of falling back to default trust.
Partner TLS trust is verified on every send: Each outbound AS2 send over HTTPS performs a fresh TLS handshake. A certificate that the partner rotates, or one that is replaced in the certificate store, therefore takes effect on the next send without a redeploy or a restart.

AS2 Connector Logs identify encrypted and signed messages regardless of server locale: On servers running with a Turkish locale, an inbound AS2 message whose content type was sent in upper case could be labelled as unencrypted or unsigned in Connector Logs. The content type is now compared independently of the server locale. Message processing itself was not affected.

AS2 scheme and TLS certificate stored with the flow and carried through export and import: The scheme and the TLS certificate selection of an outbound AS2 node are stored with the flow. On export the certificate travels by name, like the other AS2 certificate references, and is matched to the local certificate on import. If the target environment has no certificate with that name, the import succeeds with a warning that the TLS certificate reference could not be resolved; the certificate must then be selected again, and sends are refused until it is.

Flow-level Grafana dashboard: A new MIP — Flows dashboard is keyed on the flow ID, the name you give an integration, and answers whether a given flow is delivering. The existing dashboards are keyed on internal route identities, which do not map one-to-one to flows. The flow status metric is written when a run ends, so messages still in DELIVERING state are visible only in Message Monitoring.
Backend alert rules: Ten alert rules over the backend application metrics are added. One of them fires when the application metrics are missing altogether, for example when METRICS_EXPOSURE is left at its default of deny, so that the remaining panels and alerts cannot go quiet unnoticed.
Dashboard corrections: Endpoint panels exclude the platform's internal hops and timers, so real integration targets are no longer pushed out of the list. Panels show totals over the selected time range instead of five-minute rates, so earlier traffic stays visible. Empty flow panels state that there has been no flow traffic yet, per-pod tables show how work is distributed across replicas, and all dashboards share a crosshair.

Alerting configuration is loaded on a clean installation: On a fresh installation the initial alerting configuration was skipped, and the Grafana Alerting pages reported "alertmanager config was not decoded". The configuration is now loaded when none exists, and an existing configuration is left untouched.

1.18.2.15 is a stable release. Previous: 1.18.2.14