When a server is assigned to multiple overlapping or active maintenance windows, its maintenance status may be calculated incorrectly.
Specifically, if the server is removed from one active maintenance window but is still actively included in another ongoing maintenance window, DXO2 erroneously evaluates the server's status as "Not in Maintenance".
This can lead to unexpected alerts, monitoring gaps, or unintended automated actions executing on the server while it should still be shielded by the remaining active maintenance window.
This issue has been identified as a software defect and is tracked under DE675754. The system logic currently fails to evaluate the cumulative state of all active maintenance windows for a single asset when a state change (removal) occurs in one of them.
The Engineering and Development teams are actively working on a code fix for this issue.
The issue has been successfully reproduced in-house across both SaaS and On-Premises deployments of DXO2.
Subscribe to this Knowledge Base article to get further updates.