HotLoop Flow 2.15.0 release notes
HotLoop Flow 2.15.0 gives FlowLab a database sink that keeps what a database misses and a replay of a finished run, puts the editor and the node text in 13 languages besides English, and adds one MCP tool for the replay. It is amd64 first, with arm64 following in 2.15.1.
What’s new
Section titled “What’s new”- Postgres out for FlowLab diagrams (#193). The new
dia-postgres-outnode writes each record a diagram holds as one row of a PostgreSQL or TimescaleDB table, through thehotloop-flow-postgresserver the postgres node already uses. A record’s fields go in the columns of the same name, or in the columns you list, and a time column gets the time the row was made. Mark the node durable and a row the database misses is written to disk and inserted, in order, when the database is back, even across a restart. A backlog is written 256 rows to a statement. In our test, 30,000 rows waiting on disk, the size of five minutes at 100 a second, were all written in order 5 to 7 seconds after the database came back. A row the database refuses for what is in it, such as a key that is already there, is let go with adiagram.row_rejectedaudit event that carries the row, so one bad row does not stop the log. A missing table or a wrong password is not that: those rows wait. - Replay last run (#193). A diagram run now records every node start and finish and every value that crossed a wire, up to the first 20,000 events. Replay last run, in the diagram bar, plays it back on the canvas at the speed you pick.
GET /diagrams/{id}/traceserves the same recording, and the MCP toolget_diagram_tracereads it. A diagram that has not run since it was deployed answers 404. The recording is the last run’s and is not kept across a restart. - 13 languages besides English (#192). The editor, the node names, labels and help, and the dashboard page are in English plus Spanish, French, Italian, German, Norwegian Bokmal, Bulgarian, Greek, Korean, Japanese, Vietnamese, Hindi, Simplified Chinese and Arabic (right to left). The picker is in the editor, and the first visit follows the browser’s language. Text a language has not been given shows in English. The translations are first drafts without a native-speaker review, and some are marked for one.
- FlowLab’s roadmap (the roadmap, phase 9) now shows the FlowLab work that has shipped since 2.10.0 as done. The one box still open is a day on a Pi.
What changed
Section titled “What changed”- The diagram bar has a Replay last run button, a Stop replay button and a speed choice. Nothing else about running or debugging a diagram changed.
- The MCP endpoint serves 41 tools of Flow’s own, up from 40:
get_diagram_traceis the new one (#190 added the diagram and instrument tools, and every admin route is now a tool or is named in a test as one a person has to make). - The
LICENSE,NOTICE, the readme badge and the chart maintainer now name HotLoop LLC as licensor and maintainer under the HotLoop Source License Agreement 1.0, with EmberNet, HotLoop’s Gold Licensee, athelpdesk@fireballz.aias the contact (#186, #188). The terms are the license’s own and no behavior changes. These files ship inside the image. - An MQTT reconnect sends each subscription again, with a growing wait, until the broker answers or refuses, where it used to send once and drop the error (#180). A connection that timed out on a loaded broker no longer stays connected and deaf.
- The new node wears a drawn
dbsymbol on the canvas, like every other FlowLab node. - The static binary is 51,757,218 bytes (49 MiB), under the 50 MiB budget in
ci.yml, which moved up from 46 MiB for the language catalogs. - Tests and documents only: the timing tests judge the clock and not a sleep (#191), a flow’s dashboard exports from one install and imports into another unchanged (#189), the hardware caveats in the readme are closed because Flow ran on bare metal on 2026-11-17 (#182), and the readme says where Flow stands without naming a customer (#183).
New settings
Section titled “New settings”None.
Upgrade
Section titled “Upgrade”A plain helm upgrade to the 2.15.0 image and chart, or the new tag in your Quadlet unit. Nothing happens on first start and nothing needs migrating. A flow file loads and saves byte for byte as before. This release is amd64 only: arm64 boxes stay on 2.14.1 until 2.15.1, which is the same code with the arm64 image added. A browser asking for a language we have gets it on the first visit, and the picker changes it.
Image: ghcr.io/hotloop-io/hotloop-flow:2.15.0, linux/amd64 first, with arm64 following in 2.15.1. Chart: https://hotloop.io/hotloop-flow/. The README at this tag has the rest, with pictures: https://github.com/HotLoop-io/hotloop-flow/blob/v2.15.0/README.md