Manufacturing Connect Edge 4.0.9

release date april 17, 2026 review the current list of docid 0jtfl0zb6wkuqhgxifjif enhancements description events added the option to disable storing event logs in the database analytics added an information overview panel for processors use the panel to view processor configurations simplified and improved the behavior of rearrange functionality for analytics processors resolved issues description devicehub fixed issue where drivers with statusregister defined by default returned empty registers when devices were imported using a template fixed issue with consistency of tab, enter, and arrow key behavior when adding or editing a device analytics fixed issue with selecting ai processor models when editing a processor applications fixed issue where containers do not appear under the application in the catalog app page when the application was launched with more than one whitespace in name fixed issue where launching certain marketplace apps with named volumes created an extra unused docker volume fixed an issue where a container could attach to both the default and configured networks when only one network was specified removed invalid docker bridge network interfaces added during upgrades to 4 0 8 from the database to prevent network disruptions fixed issue where the container terminal returned a blank page when attempting to output raw binary data system fixed issue where templates created in manufacturing connect edge (mce) and imported into manufacturing connect (mc) could not be applied to mce instances from mc proxy urls are now correctly preserved after software updates in system > network > proxy fixed issue where static routes were lost in manufacturing connect edge fixed issue where applying a template that includes authentication or device management proxy configuration could cause a partial restore error fixed issue where support bundle downloads failed at times with a you provided 'function text() { \[native code] }' where a stream was expected error fixed issue where the system reported a success status during manufacturing connect activation, even when all individual underlying network tests failed fixed issue with increased cpu usage during log cleanup apis fixed an issue where api responses could contain different properties between tags in the same devicehub device this occurred after upgrading from 3 16 to 4 0 x