10.24.8

LTS

September 24, 2025

Mendix Studio Pro is our low-code IDE for professional developers. It's a powerful visual model-driven development environment to build apps on the Mendix Platform. With Studio Pro you can easily create, change, integrate, test and deploy your applications, all in one place. Moreover, you can manage branch lines and security as well as extend your app with custom code using the built-in editors. Click 'Download Studio Pro' to get the installer for free (Windows OS required*). Learn more about the installation and the Studio Pro capabilities in our documentation. Not a professional developer? Learn How Mendix supports different developer profiles .Before installing, please read the Release Notes to learn about improvements, bug fixes, backwards compatibility, breaking changes and known issues. *If you are using a Mac, check out these instructions first.

Release Notes - **Release date: September 24, 2025** ### Improvements - When tracing is enabled, the maximum depth of microflow calls and the maximum number of loops that are reported can be configured using the `mendix.tracing.max.microflow.depth` and `mendix.tracing.max.loop.iteration` JVM properties. The default value of these properties are `10`. The microflow call depth is calculated per runtime node and does not take into account calls made into other Mendix runtimes through REST/WebServices calls. ### Fixes - **10.24.7 Fix** — We fixed a critical issue in 10.24.7 (only) where application startup would fail when upgrading a database originally created with a Mendix version before 10.17 and using foreign key constraints. - We fixed an issue where changing a MxAdmin user's name in Studio Pro does not result in changing MxAdmin user's name in database. (Ticket 255505) - We fixed an issue where SVG images would load with incorrect dimensions. (Ticket 258901) - When using Oracle, we no longer use `dbms.lob_substr` in the generated SQL for enumeration attributes with values shorter than 2000 characters. (Ticket 259283) - We fixed an issue where database synchronization failed on SQL Server when a specialization of `System.User` was removed and there was still an `owner` or `changedBy` reference from an instance of `System.User` or a different specialization of it to an instance of the specialization being removed. * We fixed an issue affecting file saving which made named files appear untitled. Previewed file names now work as intended. - We fixed an issue in the Create object activity which would fail when creating an instance of a remote non-persistable entity in a microflow. - We fixed an issue in consumed REST services where choosing an OpenAPI contract without any operations would result in an error. - We fixed an issue where a warning was logged on startup about an already registered Jetty gauge when multiple listening addresses are specified. The connection metrics for Jetty are added per listening address and they now contain a tag `port` with the port number and a tag `host` if a host is specified. This is applicable to the metrics `jetty.connections.bytes.in`, `jetty.connections.bytes.out`, `jetty.connections.current`, `jetty.connections.max`, `jetty.connections.messages.in`, `jetty.connections.messages.out`, and `jetty.connections.request`. Be aware of the fact that there are usually two listening addresses when you specify **Open to current machine** for Runtime port security, for example 127.0.0.1 and ::1.