10.24

10.24.24

Release date: August 5, 2026

Go to Marketplace

Improvements

Performance

• We improved build performance and reduced memory usage of the React client when bundling with Rspack. (Ticket 282716, 282165, 282605)

Other Improvements

• We improved the security of the module import process by validating the file paths declared in an MPK package before extraction. Packages containing paths that traverse outside the app directory or target protected directories (such as .git, deployment, or releases) are now rejected with an error.
• We fixed a bypass in the extraction-time path filter where non-canonical ZIP entry names (for example, paths containing .. segments) could evade the protected-subtree check. Entry names are now canonicalized before filtering.
• We added support for the following database versions:
  • MariaDB 12.3
  • MySQL 9.7
• We now close the App Selector before the Open App progress dialog when the Studio Pro main window is shown.
• We now delete the log files generated by Studio Pro that are older than 7 days.
• We now support the environment variables MENDIX_TRACING_FILTER, MENDIX_TRACING_MAX_LOOP_ITERATION, MENDIX_TRACING_MAX_MICROFLOW_DEPTH in addition to system properties for the Mendix OpenTelemetry Java agent extension.

Fixes

• We fixed an issue in React client mode, where snippets would not load properly when navigating to a page with the same snippet. (Ticket 281906)
• We fixed an issue that could cause an app to fail to bundle with Rspack enabled when a pluggable widget used certain Mendix modules, such as mendix/parser and mendix/session. (Ticket 282224)
• We fixed an error in offline-first (PWA) apps when a list view with an association data source was opened for a context object that had not been synchronized yet. (Ticket 283531)
• We fixed an issue where an editable condition set to Never could be lost during widget conversion. (Ticket 283552)
• We fixed an issue where Studio Pro appeared to freeze briefly when opening an app. The progress dialog now covers the full loading process.
• We fixed an issue where Studio Pro could freeze for up to several seconds during copy operations when another process held a lock on the clipboard.
• We fixed an issue in Studio Pro where publishing a microflow in a new a REST service allowed adding that service to read-only modules such as the System module.
• We fixed an issue where local file storage does not use optimal directory structure.

10.24.23

Release date: July 21, 2026

Go to Marketplace

Fixes

• We fixed an issue where projects located in a folder whose name contained special characters (for example an '&') would fail to run locally. (Ticket 275109)
• We fixed an issue in React client mode where navigating between pages with the same layout left widgets unresponsive. (Ticket 276710)
• On SQL Server, when a unique constraint or foreign key constraint is dropped, we now use IF EXISTS. This avoids an automatic rollback of the synchronization transaction in case the constraint does not exist. (Ticket 279545)
• We fixed an issue where runtime fails to finish executing a queued task started by a user if the user is deleted during task execution. (Ticket 279891)
• We fixed an issue where the native Switch widget did not render correctly on iOS. (Ticket 280839)
• We fixed an issue with PWAs using Rspack where the service worker would sometimes not be created correctly. (Ticket 282616, 282601)
• We fixed the t is not a function crash in workflow and page editors, introduced by the recent Microsoft update for WebView. If you installed an older version of the Microsoft Edge WebView as a workaround and you have no other affected Studio Pro installations, we recommend uninstalling it to prevent future compatibility issues. (Ticket 282685)
• We fixed an issue in the call web service activity and in consumed OData services that consume services using OData version 3. The XML parser now rejects DTD declarations and external entities, because a compromised server might exploit those features.
• We fixed an issue where pressing Escape to close a modal dialog would also close the sidebar.

Deprecations

• We dropped support for the following database versions that are no longer supported by the vendors:
  • PostgreSQL 13
  • MariaDB 10.6

10.24.22

Release date: June 29, 2026

Go to Marketplace

Improvements

• We fixed the issue in OData Exists queries where an XPath constraint with nested-associations would result in an incorrect OData filter. (Ticket 261698)
• We updated the .NET Runtime to version 10.0.7.
• We added a confirmation dialog when enabling anonymous user access in App Security, warning that unrestricted anonymous roles may expose data unintentionally.
• We now allow microflow and entity parameters to be optional for Java actions.
• We improved cleanup of queued tasks that are owned by missing nodes.
• Progressive web app (PWA) wrappers are now in GA. This feature allows you to package a PWA as a native app, and is especially useful when you want to keep a web-based application architecture while distributing the app through app stores. For more information, see PWA Wrapper.

Fixes

• We fixed an issue when Studio Pro was not able to find Git after fresh installation if it was run from installer. (Ticket 232343, 232540, 232452, 234800, 231989)
• We fixed an issue where a native mobile app crashed with a synchronization error on startup when a user role did not have access to a module whose entity was included in the app's offline synchronization profile. The app now completes synchronization and returns no objects for that entity, matching the behavior of the previous XPath-based synchronization. (Ticket 241791)
• In the React client, we now copy files from a pluggable widget's assets subdirectory into the widget's directory under dist/ during bundling, even when they are not directly imported by the widget. (Ticket 274514)
• We fixed an issue with the client where passing an empty string as a parameter to an on change microflow triggered an error. (Ticket 276118, 278248)
• We fixed an issue in offline apps where passing a Non-Persistent Entity (NPE) as a parameter to a server action would fail with "Object hash is invalid!" after a transparent session restore (for example, when a session expired and was automatically renewed in the background). The read-only hash key used to sign and verify NPE object hashes is now preserved across session restores via the auth token, and is only replaced on explicit logout. (Ticket 276642)
• We fixed an issue where Studio Pro crashed when pasting content from the clipboard while another application was also accessing the clipboard. (Ticket 278333)
• We fixed an issue where an app could crash on startup when a different user logged in after a previous session, due to a discrepancy between the offline database and session in some scenarios. (Ticket 280943)
• We fixed a race condition where the value setter for some widgets, for example ListView, would execute on a destroyed value store. This would cause a crash when opening pages with ListView. (Ticket 280988)
• We fixed SQLite Error 5, specifically the database is locked error.
• We fixed an issue where commit notes and metadata were empty after a rebase when there were no MPR changes and no conflicts detected by Git.
• We added a small delay between retries of saving conflicting project files due to rare occurrences of race conditions.
• We have fixed an issue where constants from protected modules were not exported when creating a portable app deployment package using MxBuild.
• We have fixed an issue where exporting a Portable App Package could fail because file copy operations were performed outside the default file-system scope.
• We fixed a rare race condition related to authtokens.
• We fixed a visual bug affecting Call a nanoflow action properties of widgets. Depending on the order in which the actions were configured, nanoflow settings of a different property would get displayed.
• We reverted the JavaScript datetime parsing fallback on date-fns parsing (introduced in 10.19) to ensure datetime parsing on the client side stays consistent and gives proper validation errors. This fix affects only client-side datetime parsing.

Breaking Changes

• Studio Pro on macOS now runs natively on Apple Silicon (arm64). Studio Pro, Version Selector, and command line tools are all built as native Apple Silicon binaries, so they no longer require Rosetta 2 translation layer, resulting in significantly improved performance. Intel-based Macs are no longer supported.

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.21

Release date: May 27, 2026

Go to Marketplace

New Features

Rspack

• We now support Rspack as a new bundler for React client applications, delivering faster bundling and lower memory usage. It is now generally available, while Rollup remains the default bundler for now. We recommend switching to Rspack via the App bundler setting under App > Settings > Runtime. The selection is stored in the app-bundler file in the project root.

Mendix Portable Runtime (GA)

Mendix Portable Runtime (previously called Portable App Distribution) packages your Mendix application as a bundle runtime package, making it portable, self-contained, and compatible with any modern container runtime - including Kubernetes, Docker, and any OCI-compliant environment.

Key Capabilities

• Simple packaging - Build a container image and deploy. No buildpack configurations or platform-specific scripts to manage.
• Run anywhere - On-premises Kubernetes, managed cloud services, local Docker - Mendix Portable Runtime behaves consistently across all of them.
• CI/CD ready - Fits naturally into existing pipelines using tools your DevOps teams already use: Docker, Kubernetes, Helm, and standard container registries.
• No proprietary tooling - Works with the open standards your teams already know.

Improvements

• We now automatically stop Gradle daemons when you exit Studio Pro, so unnecessary background processes no longer continue running. (Ticket 258422)
• Runtime nodes now automatically shut down when heartbeat updates fail or when the node's database entry is missing, improving cluster reliability and preventing orphaned nodes.
• We improved observability for retrieve and other runtime operations by including XPath constraints, entity paths, object types, and microflow names in OpenTelemetry span names.
• We clean up duplicate cluster management tasks during startup.
• We added themecache.css files to .gitignore to reduce conflicts when edited by multiple users.
• We added temporary Java files to .gitignore to reduce conflicts when edited by multiple users.

Fixes

• We fixed an arbitrary code execution vulnerability in Studio Pro. (5.4 – CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:N/I:H/A:N – for more information see Security Advisories)
• We upgraded Netty dependencies to fix CVE-2026-42578, CVE-2026-42583, CVE-2026-42587, CVE-2026-42585, CVE-2026-42584, CVE-2026-42581, CVE-2026-42580, CVE-2026-41417, CVE-2026-42577, CVE-2026-42579. (Tickets 278202, 278290, 277691, 278290)
• We fixed an issue in the Select Elements dialog of an XML import or export mapping where reopening the dialog with previously checked elements that contained inheritance or choice-type children caused a validation error "Element '…' cannot be checked without a checked child element." when clicking OK. This happened because those elements were not expanded, so their children were not loaded and could not be validated. Studio Pro now automatically expands such elements before clicking OK in the Select Elements dialog, ensuring all required child elements are properly loaded and resolved. (Ticket 268403)
• We fixed an issue with the client where passing an empty string as a parameter to a microflow triggered an error. For example, when filtering options of a combo box with a microflow, clearing the search string would trigger the error. (Ticket 271819)
• We fixed an issue where Import and Cancel buttons were not visible for certain resolutions and scalings. (Ticket 274077)
• We fixed an issue where projects located in a folder whose name contained special characters (for example an &) would fail to run locally. (Ticket 275109)
• We resolved an OS command injection vulnerability in the Git process runner reported by Veracode.
• We fixed an issue when using the Rollup bundler with the React client.

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.20

Release date: May 7, 2026

Go to Marketplace

Improvements

• We clarified the error message when upgrading solutions with files that have paths that are too long.

Fixes

• We fixed an issue where import and export mappings incorrectly showed consistency errors for microflows with unmapped optional parameters. Optional parameters now use their default values when not provided in the payload. Converter microflows must have exactly one required parameter which receives the value to be converted and may have additional optional parameters. (Ticket 250969)
• We fixed an issue when an older offline client (from a Mendix version below 10.24.17) would fail to synchronize with an HTTP 560 (Invalid JSONRequest) error, preventing the offline app from loading. (Ticket 274811)
• We added Microsoft-related MIME types. (Tickets 276471, 276598, 276604, 276958)

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.19

Release date: April 24, 2026

Go to Marketplace

New Features

Mendix Portable Runtime (Beta)

Mendix Portable Runtime (previously called Portable App Distribution) revolutionizes server deployments and simplifies local testing by packaging applications as self-contained zip files that include all dependencies, scripts, and configurations for instant deployment across any environment. This approach eliminates complex installation procedures while providing flexible HOCON-based configuration management for seamless operations across development, testing, and production environments. For more information, see Mendix Portable Runtime.

Improvements

• We added a Refresh schema button to the mapping editor toolbar. This button appears when the mapping is out of sync with its underlying schema, allowing you to update the mapping elements to match the current schema directly from the editor.
• We upgraded the BouncyCastle dependency to version 1.84. (Tickets 276629, 276631)

Fixes

• We fixed an issue where saving changes in the Select Elements dialog of an XML import mapping incorrectly allowed saving an invalid selection where a parent element was checked but its required child element was not, without showing the expected error "Element '…' cannot be checked without a checked child element." (Ticket 273820)
• We fixed an issue in the Select Elements dialog of an XML export mapping where clicking OK on a checked parent element whose required child elements had not been expanded caused the error "Element '…' cannot be checked without a checked child element." Studio Pro now automatically checks required child elements of unexpanded parent nodes before saving. (Ticket 274683)
• We added an additional fix for cases where an external keyboard would not traverse properly through elements marked as accessible on mobile devices.
• We fixed a runtime exception in Published OData when publishing an association to an object that is inaccessible due to OData security constraints.
• We fixed a runtime error in OData search queries for varchar attribute with a limited column length and a search string longer than that limit.
• We fixed an issue in the JavaScript Action Editor where multiline import statements were not parsed correctly.

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.18

Release date: April 21, 2026

Go to Marketplace

Improvements

• We improved performance when Studio Pro exports pages and layouts for the React client during deployment. Apps with many pages, layouts, or snippet calls now deploy significantly faster.

Fixes

• We fixed an issue where offline data was lost when upgrading a native mobile app from 10.18 → 10.24+ directly, or from 10.18 → 10.19–10.23 → 10.24+. The database is now automatically migrated from legacy storage paths during upgrade. (Ticket 274811)
• We fixed an issue where an app could reject valid localized dates for custom date patterns that use month names. This affected patterns with abbreviated month names such as dd MMM yyyy and standalone abbreviated month names such as dd LLL yyyy, so values like the Dutch 16 mrt 2027 10:02 could be treated as invalid.
• We fixed an issue where MxBuild incorrectly reported that the modern web client bundler stopped unexpectedly, while the React client bundler completed normally without errors.

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.17

Release date: April 16, 2026

Go to Marketplace

New Features

• We added a new runtime setting FileStorage.S3.DisableChunkedEncoding to allow disabling chunked encoding for S3 storage. (Tickets 274327, 272789)
• We added support for strict mode in offline apps (PWA and Native Mobile). Though be aware that switching strict mode on for existing offline apps, it may cause problems for existing apps that still call the old API (retrieve_by_xpath) in full synchronization as retrieve_by_xpath is not available in strict mode.
• When Studio Pro is uninstalled, residual files created by Studio Pro are now also removed during the uninstall process.
• We added support for XPath constraints in nanoflow database retrieves to follow associations from a variable, so comparisons like $var/Association = $var now work.

Improvements

Widget and Module Marketplace Metadata

We changed how Studio Pro stores Marketplace identity data for widgets. This data is now stored in a single shared file, widgets-appstore-metadata.json, located in the root of your app project, instead of inside each individual widget's .mpk file. Additionally, some Marketplace modules could have an incorrect version string in the app model, these are now corrected automatically. When you open your app, all widget files are updated, the new widgets-appstore-metadata.json file is created, and any module version strings are corrected. These will appear as changes in your version control, commit them as part of your upgrade.

Other Improvements

• We now cleanup pending MendixRuntime-UpdateScheduledEvent and MendixRuntime-DeleteScheduledEvent system tasks before synchronizing scheduled events. (Tickets 261783, 268157, 268325, 268970, 269591, 270061, 270125, 271453, 272736, 273833, 273982)
• We improved the performance of opening the entity selector dialog box. (Ticket 270854)
• We improved the Collect Support Information feature:
  • The Collect Support Information progress dialog box is now cancellable.
  • We made the Collect Support Information feature available to macOS users.
  • We added useful information to aid our support team in diagnosing issues, such as:
    • The length of the current session.
    • The size of the app.
    • Number of modules.
    • Total document count and document type breakdown.
    • If the project directory has been excluded from Windows Defender Antivirus.
• We updated the .NET runtime version installed with Studio Pro to .NET 10.0.3.
• We no longer create ProcessedTask entries for the MendixRuntime-UpdateScheduledEvent and MendixRuntime-DeleteScheduledEvent system tasks.
• We changed the level of log messages on the SystemTask log node to debug. For non-development deployments this log node was set to info, which was causing too many messages.
• We changed how popups are initially rendered in the React client. They will now not be available to UI testing frameworks until they are actually ready to be used.

Fixes

• We fixed an issue where tasks scheduled from a microflow would execute before the microflow ends. Activities that are meant to be executed in a taskqueue should always be picked up and executed after the microflow has fully completed. (Ticket 222845)
• We fixed an issue where the select all for data grid 2 over multiple pages did not work correctly when configured with a view entity. (Ticket 263928)
• We fixed an issue with strict mode when using the rollback/commit action on a page while also using an entity on a layout. (Tickets 265794, 269314, 270867)
• We fixed an error in offline synchronization when objects with sync mode set to Never are selectively synced after a full synchronization. (Ticket 266442)
• We fixed an issue where changing the queue parallelism through a microflow constant was not working correctly for cluster-wide queues. (Ticket 267097)
• We have resolved an issue where a Mendix app would crash if hoisted inside of a directory with node_modules that contain conflicting versions of packages. (Ticket 268413)
• We fixed an issue where unsupported page variables could be selected for conditional visibility or editability. A consistency error is now raised when such a variable is used. (Ticket 269180)
• We fixed an issue where an incorrect runtime warning was thrown for missing parameters during database retrieval with an XPath constraint, even though those parameters were omitted from the client request because they were empty. (Ticket 269590, Ticket 269780)
• We fixed an issue where an OQL with a UNION of more than two NULL and non-NULL expressions could fail. For example, a UNION query of three SELECTs with two NULLs and a numeric value or object ID no longer fails in PostgreSQL. (Ticket 273187)
• We fixed an issue where snippet variables were not working properly in conditional settings in snippets. (Ticket 273971)
• We fixed an issue where filtering for objects using a constraint like [not(association)] in offline apps incorrectly returned no results. (Ticket 274157)
• We now ensure all columns in all branches of the top level UNION in an OQL query have a name or alias to avoid issues with databases that require them, like SQL Server.
• We fixed an issue where the automatic update of conditional settings was not triggered correctly when using invalid local variables.
• We added a consistency error for invalid conditional settings at top-level widgets.
• We fixed an issue where using the Tab key in the multiline text area would insert a \t character into text inputs on macOS.
• We fixed an issue with navigation, when the Clear history option is enabled in the Show page activity.
• We fixed an issue with the dropdown widget not respecting the SafeArea on Android devices OS 13+.
• We fixed an issue on iOS where specific scenarios of using custom styled widgets inside containers would not show the desired styling.
• We fixed an issue where an Oops dialog appeared when re-selecting a modified JSON Structure in an import mapping. This happened after updating the JSON Structure's content and then re-opening the Select Elements dialog to select the same structure again.
• We fixed an issue where a queued task that had become incompatible was not removed from the queue and would remain stuck in Running status.
• We fixed an issue where synchronization would cause a scheduled event to be executed multiple times.
• We fixed an issue in the React client where popups would sometimes appear at the bottom of the screen instead of being centered.
• We fixed an issue where an Oops dialog appeared when copying button widgets with parameter arguments to page templates or building blocks, and when creating page templates or building blocks from pages or widgets containing such buttons.

Deprecations

• From July 6, 2026, we will drop support for the following database versions that are no longer supported by the vendors:
  • PostgreSQL 13
  • MariaDB 10.6

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.16

Release date: March 11, 2026

Go to Marketplace

Improvements

• We introduced an opt-in runtime setting MaxRetrieveAmount that limits the maximum amount of objects retrieved by database data source operation. (Tickets 236618, 247111)
• We improved the resizing behavior of object list grids when editing pluggable widget properties in Studio Pro. These grids now resize when their dialog windows are resized. This enhancement, for example, improves the resizing of the Columns grids in Data Grid 2 widgets.
• Studio Pro has been updated to run on .NET 10 instead of .NET 8. As a result, .NET 10 is now a required prerequisite for the application.
• We improved handling of cases where a user is deleted concurrently while a session is retrieved for the same user.
• We improved the Set all to toggle in the entity access rules editor so that when some members have access rights and others do not. Now, the toggle disables all rights instead of enabling them. This prevents the Write toggle from unexpectedly affecting read access.

Fixes

• We fixed an issue with data sources where non-committed specialization objects with associations would cause a system administrator error pop-up in the client. (Ticket 262690)
• We fixed an issue where an Oops dialog appeared with conditional editability settings when a page contains multiple widgets with the same name, for example as a side effect of a merge. (Ticket 264502)
• We fixed an issue where, when re-running an app, an error would be thrown when the browser's session storage quota was exceeded because the object cache was too large. We now log this error to the console and reload the app without preserving state. (Ticket 264656)
• We fixed the NullPointerException which occurred when a session token was being generated but the user name was changed in the meantime. (Ticket 265403)
• We fixed an error affecting offline Retrieve actions when the entity was not accessible to the current user. (Ticket 266127)
• We fixed an issue in database retrievals with constraints in offline apps that caused empty result sets when the constraint referred to an association defined on a generalization of the entity of the database retrieval. (Ticket 267432)
• In the logic editors, we fixed an issue affecting users extracting submicroflows if the sequence flow in the original microflow had invalid condition value, and the extracted microflow was missing one. (Ticket 269233) We fixed an issue where long-running after-startup microflows caused other nodes to assume it had crashed. (Ticket 269993)
• We fixed an issue where an Oops pop-up window was displayed when a widget with a data source contained expressions referring to unavailable variables. (Ticket 270865)
• We fixed an issue where SVGs failed to render in offline profiles.
• We fixed an issue where access denied exceptions could occur during rebase, merge, cherry-pick, revert, or feature branch merge operations.
• We fixed an issue that when a document was modified on one source and deleted on other during a combination process, users lacked the option to resolve a conflict by deleting a document
• We fixed an issue when, after performing a rebase or cherry-pick when user did not close the push notification bar and started with new combination operation, they could end up with two visible notification bars.
• We fixed an issue with the Native ListView widget where, due to a race condition, items would not consistently load beyond a certain threshold.
• We fixed an issue where bundling protected modules used in App Modules would not include JavaScript Actions and other dependencies as expected.
• We fixed an issue where deleting a duplicate navigation profile would delete the wrong duplicate profile.

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.15

Release date: February 9, 2026

Go to Marketplace

Improvements

• We have improved the performance of session cleanup.

Fixes

• We fixed an issue where System.UserRole's Description attribute was not readable. (Ticket 259857)
• We fixed an issue where the short revision hash of the commit was being sent when deploying a package. (Ticket 264621, Ticket 266012)
• We fixed an issue in offline apps that could result in errors like "[Synchronization] SQLiteError: table mx10414574138294561$_guidToTable has no column named inaccessibleAttrs" by ensuring database migrations happen properly for all users in the client database. (Tickets 264910, 265393, 269740)
• In the logic editors, we fixed an issue where extracted microflows did not contain all the expected parameters for a newly-created activity. (Ticket 265542)
• We fixed an issue with the tab container widget. It would reset to the first tab when returning to the page, causing data sources to reload unnecessarily and other tabs to be blocked. (Tickets 266083, 266090, 267249)
• We fixed an issue where the last attributes were truncated in entity properties dialog boxes. (Tickets 266554, 260953, 256106, 251278, 255882)
• We fixed an issue where an import mapping would not read JSON attribute values when a JSON attribute was preceded by another attribute with an attribute name that is a prefix (for example StatusId and Status). We also improved how JSON objects were read when one object name was a prefix of another object name. (Ticket 266571)
• In the logic editors, we fixed an issue where Show Message activity had an empty caption after initial loading of the microflow. (Ticket 268024).
• We fixed an issue that caused setting the image of a building block to show an error dialog instead of resizing the image. (Ticket 268856)
• We fixed an issue in Maia chat where it crashed if the Studio Pro Version attribute was missing in a reference.
• We fixed scenarios in Android where navigating fields of a data view (of different types) would not be possible using an external keyboard.
• We now parse StdOut and StdError streams separately when calling git process. This improves the stability of git operations.
• We fixed an issue during local development where system texts would not be updated in the application when hot-reloading. They are now correctly updated without the need to fully restart the server.

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.14

Release date: January 16, 2026

Go to Marketplace

Improvements

• We introduced a new log node named SystemTask for logging system management actions.
• We improved the performance of runtime statistics collection.
• We improved the scheduling of cluster node management actions.
• We aligned the order of the options of the Use React Client setting with the order of other settings.
• We improved the performance of the Best Practice Recommender. It now runs faster and uses less memory.
• We improved the performance of documents operations (add, rename, delete, and more) in the App Explorer.
• We added batching to the session keep-alive and last action execution update maintenance tasks. The batch size can be changed using the SessionKeepAliveUpdateBatchSize and LastActionExecutionUpdateBatchSize runtime settings.
• We changed the timing of initializing Micrometer gauges during Runtime startup. Previously, the gauges were initialized too early in the startup sequence which would lead to the following warning message; Failed to apply the value function for the gauge 'mx.runtime.stats.sessions.named_user_sessions'. Now, gauges are initialized after the database connection has fully initialized, which also gets rid of the warning messages in the logs.
• We now support tags for the tcpjsonlines log subscriber. These can be configured with the tags property in the configuration of the log subscriber.
• We now include tracing information for the tcpjsonlines log subscriber, if includeTracingInformation is set to true when creating the log subscriber. Additionally traceIdAttribute and spanIdAttribute can be passed to configure what the attributes of the trace and span ids should be in the output JSON log.

Fixes

• We fixed an issue that caused slow serialization of Mendix objects in microflow responses when entity access was not applied during retrieval. Serialization speed is now comparable as when entity access is applied. (Ticket 226097)
• We fixed an issue where the Find Advanced > Unused Items feature would list enumerations as unused, even when they were actually used (in Microflow expressions). Now, enumerations whose values are used in your project are no longer falsely reported as unused. (Ticket 253576)
• We fixed an issue where creating a new branch from a tag was not working. (Ticket 259691)
• In the logic editors, we fixed a performance issue while running a project with many microflows locally. (Ticket 259254)
• We fixed an issue where a view entity loaded without entity access would throw an exception if used in a location that requires entity access. (Ticket 260557)
• We fixed the issue where typing in a Dataset document was slow, causing delays in displaying each character. (Ticket 263330)
• We fixed an issue where Studio Pro repeatedly displayed the error “OQL View Entity is out of sync with the OQL Query” even after syncing the query. The error would reappear after reopening the app, causing confusion and unnecessary sync attempts. (Ticket 263811)
• We fixed an issue where write permissions could not be removed for attributes that were converted to read-only types (such as AutoNumber). (Ticket 265906)
• We fixed an issue where sorting by column did not work after using the text search on a grid. (Ticket 266400)
• We fixed an issue where Studio Pro could crash when importing a font for an icon collection. (Ticket 266772)
• We fixed an issue where an incorrectly configured placeholder text did not show a consistency error and could result in an error during deployment. (Ticket 266923)
• The OQL function DATEPART with MILLISECOND now also works on HSQLDB and SAP HANA.
• We resolved an issue where passwords, when having write access for the password attribute, could be modified directly through the synchronize_objects API.
• We fixed an issue with modern client offline apps that caused data sources of the home page to be executed too early, causing errors because the offline system was not fully initialized.
• We fixed an issue that was causing excluded modules to be included in the main.scss when generating layered CSS
• We fixed the check version functionality which allowed users to perform version control operations on either revisions created on older Studio Pro versions, or on files with invalid metadata:
  • Affected operations are: rebase, merge, merge feature branch, cherry-pick and revert.
• We added keyboard accelerators to the Find Usages and Show Call Hierarchy options in context menus.
• We fixed an issue in the logic editors in the Change Object dialog where setting lists of objects through the Generate dialog incorrectly showed an error.
• We fixed an issue where during runtime on iOS, the runtime URL would not get properly created when there were more path parts included.
• We fixed an issue where an Oops pop-up window was displayed when Edit > Find returned new JSON structure documents.
• We fixed an issue in Import mapping and Export mapping in Studio Pro where elements except first of the child array in JSON were omitted.
• We fixed a bug that caused exceptions when undoing the addition of custom widget to a page (from the recommender, Maia, or Ctrl + Drag and Drop) while the properties tab was open and that widget was selected.
• We now correctly set the log node name as the node attribute and the exception cause as the cause attribute for the OpenTelemetry log subscriber.
• We fixed an issue where calling the get_license_information while using a SALT license would cause an error.
• We fixed an issue where offline objects with GUID identifiers were sent to the server when a microflow was called from within a nanoflow, causing a "Global identifier should be a number" error. These unsynced offline objects are now filtered out before being sent. (Ticket 267059)

Breaking Changes

• Curly braces in a placeholder text (for example, {Name}) must now be escaped with an extra opening curly brace (for example, {{Name}) to prevent the text from being incorrectly interpreted as a placeholder expression.
• We upgraded the AWS S3 library used for S3 file storage backend from version 1 to 2. This new version of the library has stricter configuration handling and only supports AES for client side encryption. More information can be found in Amazon S3 SDK Upgrade and S3 Storage Service Settings.
• Added a consistency check for code actions that have a file name that does not match the casing of the document name, which could cause issues on certain operating systems and when deploying to the cloud environment.

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.13

Release date: December 2, 2025

Go to Marketplace

Improvements

• We added support for the following database versions:
  • PostgreSQL 18
  • Microsoft SQL Server 2025
• We introduced the batch conversion capability in Studio Pro for converting the old widgets that are no longer supported by the React client.
• We now cleanup expired sessions in batches instead of all at once.

Fixes

• We fixed an error in the Studio Pro installer when the installer is checking if the .NET version is already installed or not. (Ticket 253218)
• We fixed an issue where unsaved changes of the System Text editor would be committed when running the app locally. (Ticket 259664)
• We fixed an issue that prevented some users to authenticate in Studio Pro. (Ticket 259700)
• SQLite files are now included in the service worker’s pre-cache list to ensure they are available offline. (Ticket 264140, Ticket 264910)
• We fixed an error when typing invalid values in the zoom combo box on the page editor in Structure mode.
• We fixed an issue where scheduled events with On overlap configured as Delay next would cause multiple "Skipping the update of ScheduledEvent because it's running; retrying in 7 seconds." log messages if the application was started with some time between the shutdown and the restart.
• We fixed the issue that invalid sessions without an associated user were never removed from the database.
• Only log 404 errors in development mode to reduce log noise in production environments. Server access logs should be used for 404 tracking in production.
• We fixed a bug where the File Uploader would not be clickable when nested in a container.

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.12

Release date: December 1, 2025

Go to Marketplace

Improvements

• We implemented a feature that allows filtering out spans by their name. For more information, see the Testing section of Tracing.
• The logout API in the new client mx-api now supports an optional params object with reloadOnSuccess flag. By default, mx-api/logout automatically reloads the page after a successful logout if you call it with no params object. If you pass a params object {reloadOnSuccess: false}, the automatic reload is disabled so you can implement your own custom logout flow and trigger reload yourself when needed.
• We now log a warning when runtime operation parameters are missing during a database retrieval with an XPath constraint. This can happen, for example, when a nanoflow retrieve activity uses an XPath constraint that references an associated object that is not yet available in the nanoflow scope. In such cases, that would lead to unresolvable XPath. (Ticket 260339)

Fixes

• We upgraded the JDBC driver for Microsoft SQL Server to version 12.8.2, because of CVE-2025-59250.
  • If you connect to SQL Server using integrated security in a module such as Database Connector, you may need to update the JDBC driver in userlib as well.
• We fixed an issue where OQL query parsing would fail if the query included a numeric WHEN clause without an accompanying ELSE condition. (Ticket 255719)
• We fixed an issue where XPath access rules on a view entity could lead to an "Object hash is invalid!" error. (Ticket 255889)
• We fixed an issue that caused the microflow execution to abort when the Sync to Device action failed in offline apps due to missing files. (Ticket 261053)
• We fixed an issue where undoing a widget update could lead to an inconsistent model, causing an error when attempting to reopen the project. We now prevent Undo actions for widget updates to safeguard against similar issues. (Tickets 256004, 260822)
• We fixed an issue that prevented a dialog from closing when users pressed Escape while editing an access rule. (Ticket 257016)
• We fixed an issue where conditional editability expressions in snippet calls incorrectly references variables when nested snippets were involved. (Tickets 257120, 262408)
• We fixed an issue where source maps for pluggable widgets were not included correctly in the React client bundle when Optimize bundle is set to No. (Ticket 261353)
• We fixed an issue where widgets with unbounded dynamic imports (for example, await import(path);) would result in a bundling error when using the React client. They are now marked as external, which means they will be resolved when the widget is loaded in the browser. (Ticket 261630)
• We fixed an issue for the Message Definitions editor where custom values for editable fields like 'External Name' disappeared. (Tickets 263144, 263609, 263817, 264535, 264805, 264850)
• We fixed an issue for Import Mappings and Export Mappings where after reopening and saving in the Select elements dialog previously selected elements deep in the tree structure were no longer selected. (Ticket 264531)
• We fixed an issue for Import Mappings and Export Mappings where Studio Pro would crash when the Select Elements functionality was used with recursive XML structures. (Tickets 265339, 265510)
• We now allow first-time users to use Studio Pro without logging in.
• We fixed memory leaks related to the style document editor.
• We fixed an issue in consumed OData services in Studio Pro where importing a metadata file with incorrect XML namespaces would show an "Importing..." progress dialog without ever completing the import.
• We fixed an issue where Core.getLicenseInformation().products() did not return a numeric value if the value was larger than 2147483647.
• We fixed a bug where nanoflows would not be exported when re-added to a page after a full deployment cycle. The issue occurred when a nanoflow was removed from a page during hot-reload, followed by a full deployment, and then re-added during another hot-reload.

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.11

Release date: November 4, 2025

Go to Marketplace

Fixes

• We fixed an issue where incompatible React client widgets did not display an error when they were nested inside a pluggable widget. (Ticket 253896)
• We fixed an issue where JSON Import mappings stopped finding objects. (Ticket 258507)
• We fixed an issue where the DatePicker native widget would not be displayed when using an empty default value and a visibility condition. (Ticket 259282)
• We fixed an issue where a wait-for-timer activity could get stuck when its workflow was upgraded while the activity was active. (Ticket 263288)
• We fixed a migration issue when going from 10.24 to 11.x that attempted to recreate an already existing column in a table in an offline app database.
• We fixed a bug where the JavaScript Action code editor would overlap with the errors pane after resizing it.
• We improved Studio Pro memory usage in operations that involve processing the project's structure (for example find usages and errors check).
• We fixed the following bugs in the version selector:
  • When opening a widget .mpk the file was kept on hold even after closing the dialog, preventing it to be renamed or opened.
  • Closing the "Version not found" dialog launched the selected Studio Pro version instead of just closing the dialog.
  • The Studio Pro versions were not displayed with the correct format.
• We reduced the size of the Studio Pro installer on Windows.

Deprecations

• We dropped support for the following database versions that are no longer supported by the vendors:
  • MariaDB 10.5
  • Microsoft SQL Server 2019
  • MySQL 8.0

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.10

Release date: October 30, 2025

Go to Marketplace

Improvements

• We added support for Oracle 23.
• We now avoid resetting the failed login count during login when it is already zero. (Ticket 260858)
• We increased the default size of popup dialogs that contain expression fields to allow for easier editing of the expressions.
• We have optimized the page exports for the React and Native clients. This can decrease the exported page size by up to 35%, making the resulting bundle a lot smaller.

Fixes

• We fixed a non-fatal crash in the studio pro installer when the installer is checking if the dotnet version is already installed or not. (Ticket 253218)

• We fixed an issue in the Studio Pro XPath constraint parser that incorrectly allowed associations and associated objects to be compared to Boolean values or empty, while that was not supported on the runtime. The following constructs will now lead to consistency errors:

  • [MyModule.MyAssociation = false()]
  • [MyModule.MyAssociation = empty]
  • [MyModule.MyAssociation/MyModule.MyEntity = false()]
  • [MyModule.MyAssociation/MyModule.MyEntity = empty]

  (Tickets 254830 and 258029)

• We fixed an issue in the Domain Model Editor where navigating to a specific OQL view entity with a consistency error from the Error pane would result in an error if the "Show View Entity" option was disabled. (Ticket 256365)

• We fixed an issue where trying to delete a huge number (millions) of anonymous sessions during startup would cause out of memory errors. We now delete sessions and anonymous users in batches to avoid this problem. (Ticket 257047)

• We fixed an issue where the React client would not get bundled when deploying for Eclipse. (Ticket 258470)

• We fixed an issue with Offline PWAs when using the React client where changes to the application would not be shown to the user without clearing the cache. (Ticket 260673)

• We fixed a "no such column" error when synchronizing a file or image derived entity which itself is derived by another entity with an offline synchronization mode. (Ticket 261700)

• We fixed a "no such column" error from a "CREATE INDEX" query when upgrading an offline app that has an association added to an entity. (Ticket 261700)

• We fixed an issue in the Studio Pro XPath constraint parser with the treatment of true and false . These are now treated the same as their function equivalents (true() and false() respectively).

• We fixed a memory leak that occurred when editing an action of a Microflow.

• We fixed an issue in offline apps that could result in data validations of microflow calls not being properly handled.

• We fixed an issue preventing opening apps passed as startup arguments for Studio Pro in MacOS.

• We fixed an issue where a drop-down list in a Reference Selector reopened automatically after closing.

• We fixed an issue where duplicate responsive navigation profiles could not be removed.

• We fixed an issue with using a dash - in the Organization Name of a pluggable widget.

• We fixed an issue where building an app in a different culture would result in decimal numbers changing their decimal separator.

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.9

Release date: October 6, 2025

Go to Marketplace

Improvements

• We improved the rendering performance of repeating widgets in Design mode, by only rendering a single repeat for widgets within a snippet call, parent layout, or nested within another repeating widget.

Fixes

• We fixed an issue in the React client where autofocus was incorrectly triggered by dynamically loaded widgets, causing combo boxes that use a widget with a dynamic source in their custom content to unexpectedly lose focus and close. (Ticket 254768)
• We fixed an issue where Import Mappings using 'Find an object (by key)' or 'Call a microflow' did not create an object for valid input. (Tickets 255130, 260462)
• We fixed an issue where Node.js would run out of memory during the bundling process of very large, complex applications using the React client. (Ticket 257472)
• In the logic editors, we fixed the zoom in and zoom out behaviors of error-handling icons. (Ticket 258424)
• We improved the performance of the tree control that allows you to select elements for Message Definitions, Import Mappings, and Export Mappings. (Ticket 258606)
• We fixed an issue where a Java action could still cause compilation errors, even if excluded from the project. (Ticket 259414)
• We fixed an issue where, when there were no conflicting changes, users were not properly informed and metadata was missing due to cherry picking.
• We fixed a few memory leaks in the React client, most notably when closing and open pages.
• We fixed a memory leak which occurred when re-opening a project, or switching branches in Studio Pro.
• We fixed an issue for Export Mappings where a recursive XSD structure was not properly marked as invalid in cases where more than 1000 mandatory elements were auto-selected.
• We fixed an issue in Studio Pro where restarting Windows with an open app and then opening the app again would result in a warning dialog window about the app already being open.
• We fixed an issue where task queue tasks were not able to mark themselves as completed after execution.

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.8

Release date: September 24, 2025

Go to Marketplace

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.

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.7

Release date: September 19, 2025

Improvements

• When either the X-Forwarded-Proto or X-Forwarded-Scheme header is set to http, cookies will now be set without the secure attribute, even if the ApplicationRootUrl is set to a secure URL.

Fixes

• We fixed an issue that could result in the error Duplicate objects are not allowed in the console log when synchronizing offline. Please note that the root cause of this issue is the use of background synchronization, which is not recommended for offline apps. (Ticket 235130, 251202)
• We fixed an issue in published OData services where requests that filtered based on associated data combined with 'and' would receive a response containing data that did not match the filter. (Ticket 241825)
• We fixed an issue where retrieving from database in nanoflows failed when using many-to-many associations with XPath constraint going over an association. (Ticket 253996)
• We fixed an issue where an expression could not be set when the number of available variables was too large, causing the variable list to expand and block access to the expression editor. (Ticket 254957)
• We fixed an issue where an Oops pop-up window was displayed when the page variables button was clicked in structure mode for a page template. (Ticket 255394)
• We fixed an issue where the combo box widget failed to render when the Store value is configured with a page or snippet variable. (Ticket 256493)
• We fixed an error where apps would attempt to clear their local cache while developing locally when not running in a secure context (such as localhost). (Ticket 257026)
• We fixed an issue where doing a hot reload while using the React client would lead the to deployment spinner spinning infinitely in some projects. (Tickets 257026, 257859)
• We fixed an issue where a foreign key constraint violation in the database could result in a NullPointerException. (Ticket 258430)
• We fixed an issue where some customers experienced problems logging into their native mobile apps after upgrading to Studio Pro 10.24. The app would enter an authentication loop and return the error: Could not create a session because the server responded with 401 (Unauthorized). (Ticket 258696)
• We fixed an issue where passing an empty enumeration value to a microflow executed in a task queue would cause the execution to fail. (Ticket 259170)
• We fixed an issue where data grid action buttons with empty parameters would cause runtime errors when calling microflows.
• We fixed an issue for export mappings where a user would clear a checkbox in the 'Select schema elements' tree structure, but not all children elements were deselected.
• We fixed an issue where a 404 - file not found for file: .well-known%2Fappspecific%2Fcom.chrome.devtools.json error was shown in the Studio Pro console when opening a React app in Chrome with dev tools open. This error was caused by Chrome's automatic workspace folders feature.
• We fixed an issue with the client parser API where the groups option would also require the places option.
• We fixed an issue where previous pages would not load in the React client after closing a page that was opened from a pop-up window.
• We fixed an issue where a Manifest: unknown 'display' value ignored warning was shown in the browser console when opening a non-PWA React app.
• We fixed an issue where pages with a mix of persistent and non-persistent entity parameters did not load properly the first time.
• We fixed an issue affecting file saving which made named files appear untitled. Previewed file names now work as intended.

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.6

Release date: September 11, 2025

Go to Marketplace

New Features

• The Changes pane will now automatically be updated if files on the disk are changed outside of Studio Pro.

Improvements

• We added support for converting data grid 1 columns (ones configured over reference sets) into data grid 2 columns.
• Pushing commits to the server is no longer possible if there is nothing to push.

Fixes

• We fixed a rare issue where an error pop-up window could appear if a user attempted a version control operation while Git optimization was running for an extended period of time. (Ticket 246741)

• We fixed an issue where an Oops pop-up window appeared during deployment if multiple pages using the same snippet are processed simultaneously. (Ticket 254648)

• We fixed an issue where a consistency error for offline profiles ("Specialization Entity should have an offline synchronization mode as its generalization Entity has an offline synchronization mode") was wrongly reported. (Ticket 255323)

• We fixed an issue on offline-associated entities pertaining to startsWith, which is not a function error in synchronize actions. (Ticket 257346)

• We fixed an issue where database synchronization would fail when all of the following occurred during the same deployment: (Ticket 258046)

  • An association in the database contained any dangling references
  • Foreign key constraints were newly enabled
  • The association storage was changed to or from being a direct association

• We fixed an issue where an Oops pop-up window was displayed when switching the data source type of a combo box.

• We fixed an issue when using file dialogs while the persisted file, directory, or drive no longer exists.

• We fixed an issue for Export Mappings where it was incorrectly possible to clear the Message Definition root element from the Select schema elements tree structure.

• We fixed an issue for Import Mappings and Export Mappings where a user would select a checkbox in the Select schema elements tree structure 5 levels deep or more, and the tree failed to expand itself to show children items. This made it possible to not select required schema elements.

• We fixed an issue for Export Mappings where XSD extension attributes checkboxes in the Select schema elements tree structure were incorrectly not selected when the user selected the checkbox of their parent attribute.

• We fixed an issue where importing modules containing files with paths longer than the maximum length failed to throw an error message. It will fix these support issues:

  • An issue where you cannot import the Nanoflow Commons to 10.6.x_Maintenance branch line. (Ticket 227963)
  • An issue where importing the Nanoflow Commons module is impossible. (Ticket 234259)

• We fixed an issue where the Push button is disabled after opening an app with local commits while auto-fetch is disabled.

• We fixed an issue where user gets an Oops pop-up window when creating a non-versioned app.

Deprecations

• From November 1, 2025, we will drop support for the following database versions that are no longer supported by the vendors:

  • MariaDB 10.5
  • Microsoft SQL Server 2019
  • MySQL 8.0

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.5

Release date: September 8, 2025

Go to Marketplace

Improvements

• We improved performance when summarizing conflict information for large documents.

Fixes

• Dependencies for a portable version of Studio Pro (WebView2, OpenJDK, and Gradle) are now placed inside the application's installation folder. Installing or removing a specific version of portable Studio Pro no longer affects the dependencies of other installed versions. (Ticket 244240)
• We fixed an issue for Import Mappings and Export Mappings that caused checkboxes in the Select schema elements tree structure to be set incorrectly. This happened for XML schema inheritance and choice elements. (Ticket 249795)
• We now allow filtering over reference sets for database data sources, previously allowed only for list views. (Ticket 251833)
• We fixed an issue where an entity with Synchronization Config set to Never was removed from the list view or Data grid 2 when Synchronize All was triggered (due to excessive cache deletion). For more information on synchronization, see Offline Synchronization. (Ticket 253629)
• We fixed an issue in Import Mappings where object properties were not connected correctly to mapped attributes, resulting in empty import values. (Tickets 254351, 256716, 256726)
• We fixed an issue where database synchronization sometimes unnecessarily recreated the uniqueness constraint on the primary key mapping table of an external entity. (Ticket 255223)
• We fixed an issue where an enumeration with a value or a caption set to com resulted in a compilation error when you tried running the app. We have also added this to the reserved words list. (Ticket 255976)
• We fixed the Tab Container widget to avoid loading hidden tab content when the conditional visibility expression refers to a page parameter. (Ticket 256717)
• We fixed an issue in external OData entity's object initialization where specifying the value for a key via a microflow expression failed.
• We fixed an issue where a user was asked to provide Git credentials for repository optimization.
• We fixed an error which appeared when viewing widget properties for widgets that needed to be updated.
• We improved the authentication mechanism in Studio Pro. It fixes the following issues:
  • It fixes the issue where Studio Pro on macOS asked the user credentials to get access to Keychain (passwords) for a TeamServer project.
  • It fixes the issue where the sign in dialog was displayed when committing a change in Studio Pro which was already open.
  • It fixes the PMP Git issue where wrong credentials were fetched from the Windows credentials store.

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.4

Release date: August 19, 2025

Go to Marketplace

Fixes

• We fixed a known issue where the debugger did not reconnect when restarting an app using the React client.
• We fixed a known issue when locally re-running with runtime-only changes while using the React client. They are now properly loaded by the runtime.
• We added the refresh functionality for the Marketplace content when a session times out. The reload button will now close the details page and refresh the search tab view to ensure the latest information is displayed.
• We fixed an issue in offline synchronization (using the Synchronize unsynchronized objects and Synchronize all actions) that resulted in error log statements and System.SynchronizationError objects containing a text Changing member failed for security reasons, no write access for changed member. That was caused by the offline client trying to synchronize a change for a member that was inaccessible by that user.
• We improved the exception handling of Studio Pro when necessary .NET components are missing with a user-friendly message instead of an error pop-up.
• We fixed an issue where Studio Pro crashed due to an XPath constraint being too long or complex to parse correctly. Now a consistency error message is shown instead.
• We upgraded React Native version to 0.77.3. This addresses an issue that caused the app to stop working after a reload.
• We fixed an issue when locally re-running with runtime-only changes while using the React client. They are now properly loaded by the runtime.

Breaking Changes

• We removed the numeric part of IDs in the HTML and added l or p prefixes for layouts and pages. For example, 89.PCP.MyApps_Overview.snippetCall4 will now be p.PCP.MyApps_Overview.snippetCall4 instead. The purpose of those numeric parts was to ensure uniqueness of the IDs, however, they are actually not needed here as a page and layout already have unique identifiers. Furthermore, their pseudo-random nature meant that rebuilding an application resulted in more changes than needed, limiting the cachability of Mendix applications.

Known Issues

• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.3

Release date: August 7, 2025

Go to Marketplace

Improvements

• We now remove web service user sessions if they are expired.
• The navigation tree menu is no longer tagged with aria-hidden when it is still visible.
• Menu buttons on the navigation menu are now reachable when they are visible.
• We added aria-expanded, aria-haspopup and aria-controls attributes to the navigation tree where relevant.
• We upgraded the ONNX dependency to version 1.22.0.

Fixes

• We fixed a customer-specific issue where they were unable to build using MxBuild, while they were able to use the standardized Studio Pro build. (Ticket 247544)
• We fixed an issue in the logic editors where a caption from the Show Message activity did not update when switching between languages. (Tickets 247962, 250137)
• We fixed an issue where the Back and Forward navigation feature did not work with styling-related files. (Ticket 252248)
• We fixed an issue that prevented updated workflows from being queued for execution when Mendix Runtime crashed during startup. (Ticket 253424)
• We fixed a conversion issue that occurred when upgrading apps from 9.24. Specifically, arguments of Show a page, Call a microflow, or Call a nanoflow event actions were affected where parameter mappings changed to a different selection variable on the same page. (Ticket 253494)
• We fixed an issue where a loop in a microflow did not execute if the first activity was disabled. (Ticket 253542)
• We fixed an issue where some log nodes were not be available in the Set Log Levels dialog when running a Mendix app locally from Studio Pro. (Tickets 255330, 255510, 255776)
• We fixed an error that occurred in native offline apps when upgrading from Mendix 10.12 or below.
• We added the ability to remove Mendix Studio Pro versions directly from the Version Selector interface when traditional uninstallation failed due to corrupted Windows registry paths, giving users a manual cleanup option.
• We fixed an issue where two different error messages overlapped in the Choose Branch line pane after signing in and out.
• We fixed an issue where new files created during a rebase were not included in the commit.
• We fixed an issue where you were unable to commit unsaved documents while rebasing.
• We fixed an issue where Studio Pro crashed when opening the History dialog if the metadata was corrupted
• In the Dojo client, we fixed a pop-up window resizing issue that occurred upon interacting with a combobox widget inside the popup on mobile devices.
• We fixed a conversion issue affecting sorting in the Gallery widget, specifically when upgrading the data widgets Marketplace module to version 3.0.0 or above.
• We introduced a set of pre-commit checks to ensure generated content is up to date before committing. This prevents generated content from being updated without any user input after committing, which limited the user from completing other version control operations (like a Pull from the server).

Known Issues

• In the React client, re-running an app locally with runtime-only changes does not properly apply those changes. (Tickets 253176, 253539, 253842, 253932, 254100)
  • Fixed in 10.24.4 and 11.1.0.
• In the React client, the debugger does not reconnect when restarting an app.
  • Fixed in 10.24.4 and 11.1.0.
• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.2

Release date: July 22, 2025

Go to Marketplace

Improvements

• We improved the startup performance of task queues. Pending tasks are now validated when they are executed instead of at startup.
• We improved the notification system to also alert users of third-party antivirus software (in addition to Microsoft Defender) that using antivirus software may impact system performance.
• We translated the Sign In dialog.
• We improved the quality of Korean and Chinese translations for error, warning, and deprecation messages.

Fixes

• We fixed an issue where navigating to a screen already in the navigation history caused unexpected behavior when using the Side Bar layout. (Ticket 232247)
• We fixed an issue where closing a page from a microflow triggered data source retrievals on that page. (Ticket 239900)
• We fixed an issue where uploading a SVG image caused an error. (Ticket 244585)
• We fixed an issue where the runtime log levels were not restored correctly when restarting the app from Studio Pro, in cases where the runtime had been stopped earlier due to the trial version timeout. (Ticket 251399)
• We fixed an issue where, during module import, the widget version check was incorrectly comparing different widgets. (Ticket 252131)
• We fixed an issue that caused a page to crash during navigation when using a data view widget in the page with a nanoflow. (Tickets 252234, 254377, 254487)
• We fixed an issue with MxBuild that reported successful build before the build process had finished. (Ticket 252729)
• We fixed an issue in the logic editors on macOS where pressing Command + C failed to copy the selected activity to clipboard and instead changed its caption. (Ticket 253384)
• We fixed a recurring error being caused by showing conditional hidden properties when configuring pluggable widgets through the Properties pane, such as Data Grid 2 columns. (Tickets 254074, 254426, 254632, 254637)
• In the logic editors, we now correctly update the toolbox when the exposed Java or JavaScript action info changes.
• In the logic editors, we fixed an issue where the sequence flow control points overlapped with the connection points unintentionally in some cases.
• We fixed an issue when there are some files left after aborting a merge, cherry-pick, or revert operation on a commit. That caused an ERROR in STP. Now the files are reset to the initial state after aborting any of the mentioned operations.
• We now save a file name when saving a document offline.
• We fixed an issue with online entities used in offline apps where associations from online entities to offline entities resulted in errors while saving data and calling microflows (errors like java.lang.NumberFormatException: For input string: "GUID:[...]").
• We fixed an issue where in some scenarios, the import of a module containing widgets overwrote the widgets in the project without checking the version.
• We fixed an issue in the App Selector where users encountered crashes and error messages while trying to Choose Branch Line of an app after switching between different user accounts.
• We fixed an issue where dbms_lob.substr was unnecessarily applied to limited String attributes when running SQL queries in Oracle.
• We now correctly render the warning message for the association storage in the association properties dialog. This was not word-wrapped, which caused part of the text to be unreadable.
• We fixed an issue with Maia for Pages where it did not properly take the previous API output into account, which could lead to errors during subsequent requests in the same conversation.
• We fixed an issue where selecting Resolve conflict using server for a conflicted file did not solve the conflict.
• We fixed an issue with the React client logging a message to the console to download the React Devtools when opening an app locally.
• When upgrading to a data widgets module version 3.0.0 or above, we fixed an issue where the configuration of drop-down filter settings for associations on Data Grid 2 columns was not converted correctly to the drop-down filter widget of the new setup during Data Grid 2 widget updates.

Known Issues

• In the React client, re-running an app locally with runtime-only changes does not properly apply those changes. (Tickets 253176, 253539, 253842, 253932, 254100)
  • Fixed in 10.24.4 and 11.1.0.
• In the React client, the debugger does not reconnect when restarting an app.
  • Fixed in 10.24.4 and 11.1.0.
• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.1

Release date: July 4, 2025

Go to Marketplace

New Features

• We added support for access keys in context menus for commonly used editors: domain model, microflow, page, mapping, and workflow.

Improvements

• We improved the order of the items in the Go To dialog in Studio Pro when searching, to make more relevant items appear higher in the list. (Ticket 221215)
• In the logic editors, we now include Change Object actions when finding entity usages. (Ticket 249539)
• We made the following improvements in the logic editors:
  • When resizing an element, connected annotations are now moved the same way as other elements.
  • When expanding loops after inserting elements into them, connected objects are now also moved aside.
• We relaxed the restriction that entities with an online synchronization mode could not refer to entities with an offline synchronization mode. It now only prevents XPath constraints in pages and nanoflows that mix entities with online and offline synchronization modes allowing more modeling possibilities.
• We enhanced the version control portfix functionality by integrating the Git CLI to perform this operation. This update optimizes the process and improves the overall stability of the portfix functionality.
• We improved the Java API for implementing CSP in modules. The configuration API was expanded with getHeader and getCustomHeaders methods for interacting with custom headers and we added a CSP API to the Core class that contains the getTemplate, getNonce, hasNonce, and addHeader methods.
• We updated the bundled Node.js from v20 to v22.
• We defined a list of associations: System.WorkflowActivityRecord_Actor, System.WorkflowActivityRecord_TaskAssignedUsers, and System.WorkflowActivityRecord_TaskTargetedUsers. Non-persistable objects referencing the current user through any of these associations will no longer be prevented from being garbage collected.
• When upgrading to a data widgets module version 3.0.0 or above, we fixed an issue where grid-wide filtering configuration was not converting correctly to the new setup when filter widgets were wrapped (for example, in a container) during gallery or data grid 2 widget updates.

Fixes

• In the microflow editor, we now correctly show the Continue error handler on Call microflow actions. (Ticket 247917)
• We fixed an issue where trying to auto-commit external entities threw an exception. After this fix, all external entities will be excluded from being auto-committed. (Ticket 250591)
• We fixed an issue for Import Mappings and Export Mappings that caused checkboxes in the Select schema elements tree structure to be set incorrectly. (Tickets 251136, 250682, 227036, 250266)
• We fixed an issue in consumed OData services where clients reading large amounts of data led to errors related to database connections. (Ticket 251379)
• We fixed an issue where an attempt to retrieve more than 500 external objects by ID at once failed. For example, when retrieving many external objects by association. (Ticket 251911)
• We fixed an issue in offline synchronization that could result in error log statements and System.SynchronizationError objects containing a text Changing member failed for security reasons. No write access for changed member, which was caused by the offline client trying to synchronize a change for a member that was inaccessible by that user.
• We fixed an issue where Studio Pro on MacOS crashed if the Java Development Kit was not installed.
• We fixed an issue where conflicting versions of userlib jars did not give a consistency warning if the project had no managed dependencies configured.
• We fixed an issue where the tracing service name configuration could not be changed.
• We fixed an issue where some OpenTelemetry configurations did not apply.
• We fixed an issue where HTML anchor and area elements without a href attribute interrupted the autofocus behavior, not allowing users to focus to the next item in order.
• We fixed an issue in the React client, where autofocus did not work when navigating to another page.

Known Issues

• In the React client, re-running an app locally with runtime-only changes does not properly apply those changes. (Tickets 253176, 253539, 253842, 253932, 254100)
  • Fixed in 10.24.4 and 11.1.0.
• In the React client, the debugger does not reconnect when restarting an app.
  • Fixed in 10.24.4 and 11.1.0.
• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23

10.24.0

Release date: June 26, 2025

Go to Marketplace

New Features

• We updated the filter button in the Go to... dialog to show whether there are active filters.
• In the logic editors, pressing Shift while dragging objects from the App Explorer, Toolbox or the toolbar will disable snapping the objects to other objects.
• The feature to access online data in offline apps is now generally available. For more information, see Offline-First Data
• We changed port fix to cherry pick to be more aligned with git and added recognition of cherry pick and revert operations into the topbar.
• We enabled native mobile builds for PMP customers.

Improvements

• We added error logging when a page fails to be loaded in the React client when navigating to it. This can happen when a page includes a widget with a corrupted bundle. (Ticket 245516)
• We integrated the modernized access rules editor into the entity Properties pane.
• When updating pluggable widgets, Studio Pro will now try to preserve the values of properties that change type between versions. This is done when the property types are compatible.
• We improved Maia for Pages to support the Charts, Data Grid 2, Image, and Combo Box widgets, provided they are already installed in Studio Pro.
• We made various improvements in the logic editors:
  • We added the option to hold the Shift key to display connection points on hover.
  • Making an element smaller automatically repositions its connected elements to preserve the width of the sequence flows between them.
  • When inserting elements into a flow, connected elements and unconnected elements in the same container are now moved to make space.
• We bundled OpenTelemetry agent jar with Studio Pro. It can be found under runtime/agents/opentelemetry-javaagent.jar.
• We provided the Enable Tracing option to enable runtime tracing in Studio Pro. It can be accessed through App Settings. For more information, see the Minimal Configuration section in Tracing.
• We no longer close the response writer of custom request handlers, if an asynchronous request is started. With this change it is possible to implement asynchronous request handlers.
• We implemented an OpenTelemetry agent extension that provides default settings. It can be found under runtime/agents/mendix-opentelemetry-agent-extension.jar.
• We now add consistency warnings if there are multiple versions of the same Java dependency in your app.
• When importing a module, widget, solution package or when starting a new app from a template, we now prevent the package from unpacking content to undesired directories. The user can still choose to extract the rest of the package.
• We now highlight an access rule that is opened from the Changes or Error pane in the modernized entity access rules editor instead of directly opening it.
• We improved error reporting for React client. Now you can see JS actions and widgets related errors directly in Studio Pro without having to open application logs.
• We log a warning when starting an app if there are still file documents on the local file system which were created before Mendix 5.12. Make sure all these files are migrated before upgrading your app to Mendix 11, as apps with these files will not start anymore under that version. Files are migrated automatically in the background when running apps on Mendix versions from 8.14.0.
• The Chinese, Korean, and Japanese versions of the Studio Pro UI are now in General Availability. Please see documentation for more information.

Fixes

• We fixed an issue where hidden pluggable widget properties were not reset correctly. This resulted in translations that caused widget update notifications, missing translations in Data Grid 2, and unused properties creating consistency errors in File Uploader. This fix ensures that these properties are reset when hidden with default values, and applied only when they are used. (Tickets 233401, 248682)
• We fixed an issue where Safari extensions broke the Dojo client. (Ticket 246247)
• We fixed the issue where the size of the offline database was not reduced enough after a sign-out operation. (Ticket 247029)
• We fixed an issue where Studio Pro closed after a user logged in. (Ticket 248086)
• We fixed a caching issue for React applications that had precaching enabled. (Ticket 250116)
• We fixed an issue where enumeration values with the name Core caused compilation errors. (Ticket 250532)
• We fixed an issue that native apps upgraded from prior versions to Mendix 10.19-10.23 got an error that prevented the native app to start.
• We fixed an issue where the Show button did not work in dialogs when selecting an entity.
• We fixed an issue in the React client where local reruns hung after making changes to a recursive nanoflow.
• We fixed an issue with using JavaScript actions in a protected module when using the React client.
• We fixed an issue where an association source in a data grid or template grid stopped displaying data after previously shown data was cleared due to an unavailable context object. (Ticket 250338, 250479)
• We fixed an issue where the Mendix Home button in Open Global Navigation redirected you to My Apps instead of the home page.
• We fixed the text Renaming that was also shown when adding a new document, instead we will display Checking name.
• We fixed an error that occurred in the Published OData Service document when changing the documents properties.
• We fixed an issue where Studio Pro closed when adding an SVG file to the Image Collection document.
• We fixed an issue in the Consumed REST Service document where an error was displayed after pressing Send for specific requests. This issue occurred when receiving empty content for a request that was already connected to an entity before.
• We fixed an issue in the domain model editor where an unexpected exception closed Studio Pro rather than showing the exception in a dialog.
• We fixed an issue in OQL view entities where Studio Pro showed the type of the AutoNumber column as Number. It now shows it as Long.
• In the logic editors, we fixed the following issues:
  • We fixed an issue where an error pop-up window was shown when dragging items from the toolbar into the working area of the editor.
  • We fixed an issue where a parameter was connected to an activity causing Studio Pro to crash.
  • We fixed an issue where the Change Variable action could be added through Maia for a variable that could not be changed. For already existing erroneous actions, we now show a consistency error instead of a pop-up window.
  • We fixed an issue that caused incorrect placement of flows and events when adding a Decision through the Logic Recommender.
• We fixed an issue in offline apps that caused a query error if access rules restricted access to certain attributes of a generalized entity in an inheritance hierarchy.
• We fixed an issue where microflows tried to use online data in native pages which did not allow for such usage.
• We fixed an issue where converting a nanoflow to a microflow did not trigger a warning when the nanoflow was used in a native page or layout.

Deprecations

• We deprecated the Document templates and the Generate Document actions.
• We deprecated the following methods of the class com.mendix.core.actionmanagement.internal.InternalCoreAction: setContext(IContext), addDatavalidationFeedback(IMendixIdentifier, Map<String, String>), addDataValidationFeedback(DataValidationInfo), handleConcurrentExecution(), setEventObjects(List<IMendixObject>), getMetaInfo(), setMetaInfo(JSONObject), setActionName(String), getException(), setException(Exception), getState(), setState(ActionState), setAllowsConcurrentExecution(Boolean), clone(). There is no replacement as these method were meant for internal usage only.

Known Issues

• In the React client, re-running an app locally with runtime-only changes does not properly apply those changes. (Tickets 253176, 253539, 253842, 253932, 254100)
  • Fixed in 10.24.4 and 11.1.0.
• In the React client, the debugger does not reconnect when restarting an app.
  • Fixed in 10.24.4 and 11.1.0.
• A known issue occurs in two ways due to the t is not a function. Please Close and reopen this UI component. If the issue persists, contact Mendix Support. error introduced by Microsoft Edge WebView 2 version 150:
  • When creating a new workflow, the error above occurs. The workflow is created but the editor does not open, preventing further development activities.
  • When opening the Workflow Recommender or the UI Recommender, the error above occurs, breaking the editor and preventing further development activities. Closing and opening the editor will clear the error.
    • Fixed in 10.24.23