Version 1.18.1.3
Release Date: September 4, 2026
Release Type: Stable
Previously published as: 1.18.8 (image tag staging-1.18.8)
Connector Logs now cover flows started by a poll and identify every step with a step code, and System Logs gain a correlation column and a column order that matches the written log line.
Backend Server
New Features
- Connector logs for flows started by a poll: A flow started by a polling connector previously had no connector log at all, even with connector logging enabled. The poll cycle is now recorded as three steps, Poll Started, Poll In Progress and Poll Ended, around the connect, list and fetch steps. The closing step is written on every path, so a poll that failed can be told apart from one that is still running. Every message a cycle delivers carries the full account of how it arrived: which cycle, on what schedule, how many items came with it and how long it took.
- Step codes on connector log steps: Every connector step now carries a stable step code (prefixed
MIP_) that identifies exactly which step a row belongs to, even when a connector performs the same type of step more than once in a run, such as two sends on one AS2 connector. The code does not change with the outcome of the step. When a step fails, the system log names the same code next to the error type, so a Connector Logs row and a system log line can be matched.
Frontend Server
New Features
- Step code in the connector log API: Connector log entries read through the server now include the step code recorded by the backend, passed through unchanged.
Frontend Web
New Features
- Step Code column in Connector Logs: The Connector Logs table gains a Step Code column directly after Step Type. Step Type tells the kind of step and can repeat within a run, while Step Code tells which step it was. The code is shown exactly as recorded, so it can be searched for in the system log. The step number is now the first column of the table.
- System Logs show correlation data and follow the order of the log line: The System Logs table now lists its columns in the same order as the written log line, with Thread before Logger. A new Correlation column, placed between Thread and Logger, shows the flow reference of a log line with the trace and span ids in a tooltip, so a line can be tied to the message it belongs to.
1.18.1.3 is a stable release. Previous: 1.18.1.2