Skip to main content
Feedback

Flow Release Notes for September 2025

Platform Release

September 13 2025
New
We added these features

  • Increased the maximum file size for the file upload component, allowing you to upload files up to 1GB in size. (FLOW-8497)

  • As of this release, the minimum officially supported PostgreSQL version is 17+. (FLOW-8482)

  • Added an Export Flow button to the main Flows list screen, allowing you to export the Flows. (FLOW-8456)

  • Added the ability to view MCR node information in the Token edit UI, providing greater visibility into the nodes running MCR. (FLOW-8454)

  • Removed the ability to create subtenants at design time using a feature flag. With the feature flag enabled, you cannot create new subtenants. (FLOW-8427)

  • Added the ability to generate a Docker Compose file and a Docker run command as part of the MCR node installation process, enabling you to easily spin up an MCR node with the necessary configuration. (FLOW-8414)

  • Added support for clickable outcomes to charts in runtime, enabling you to interact with and explore data more effectively. (FLOW-8511)

  • Removed the auto-increment requirement for SQL Service tables, enabling more flexibility in table design. (FLOW-8524)

  • Added the ability to specify a non-root user in the generated Docker command for local runtimes, defaulting to the "flowuser" user with the "flowgroup" group. This ensures the generated Docker command is valid when pasted into a command shell. (FLOW-8525)

  • Added an 'isColumn' boolean to Custom Components, allowing you to specify whether a custom component is intended for use as a standalone component or as a column component in tables and datagrids. (FLOW-8536)

  • Added support to package large flows, enabling you to import and export larger flows in a new .package2 file extension. (FLOW-8531)

  • Added the ability to include custom components within table cells, enabling you to create more dynamic and interactive tables. (FLOW-8530)

  • Added additional prompts and checks when publishing a public flow. The flow developer will be prompted to enter the word public to ensure they intend to publish their flow without authentication. (FLOW-8547)

  • Added new icon on the flows screen to show if a flow is public or protected by authentication. Please note, this icon is for information only and has no impact or change to your flows behaviour. (FLOW-8548)

  • Updated the MCR base image to Alpine OS, providing better performance and enhanced security for users. (FLOW-8553)

  • Introduced new MCR cloud connection logic to improve connection robustness. Enables new leader logic for multi node clusters. (FLOW-8544)

  • Added new tenant security option to suppress warning/confirmation when publishing a publicly accessible flow. (FLOW-8588)