Version 1.18.2.9

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

Flow metrics now count handled errors as failed runs, and the MongoDB connector works end to end.

Flow metrics count handled errors as failed runs: The mip_flow_messages_total metric reported every run as a success, even for flows that failed on every message, because errors taken over by the flow's error handling were not seen. A run that reaches error handling now counts as failed, also when an error subflow recovers it, which matches what Message Monitoring shows. One gap remains: an error inside the branches of a Splitter that does not stop on error is still counted as a success.
MongoDB connector works end to end: A MongoDB sender could not complete a run: it always returned a "Return type is invalid" error instead of the documents it had read, scheduled MongoDB senders never fired, and MongoDB destinations could fail the backend at startup because they were treated as JDBC connection pools. MongoDB destinations are now registered as MongoDB clients under their database name, and a client is closed when its destination is changed or removed.
A failing JDBC driver no longer unregisters a destination: When a JDBC destination is updated, the new data source is built before the old one is dropped, so a driver that fails to load leaves the previous connection in place.

1.18.2.9 is a stable release. Previous: 1.18.2.8