Same device event and GUID causes add hardware to hang indefinitely

When using the driver framework, if for some reason a device is added with two of the same “DeviceEvents”, the Add Hardware dialog will hang indefinitely and no errors are thrown in the recording server logs.

This makes debugging very difficult when a device has multiple event names that are identical.

To reproduce, add a device with 2 identical device events. The code will execute until the end, which means it is somewhere in the Milestone recording server code.

An exit strategy would be good :slight_smile:

Thank you for reporting this, Milestone Development will look into this.

A fix causing the Management Client to fail with an error instead of hanging will be included in the 2025 R1 release.

Thanks so much for having sorted this out so quickly!