SubmissionQueueLengthMonitor shows “System.ArgumentException: Transition timeout…” in Exchange Server 2019 and 2016


After you use the Suspend-Queue cmdlet to stop processing on a queue in Microsoft Exchange Server 2019 or Exchange Server 2016, more than 100 messages stuck in the submission queue but no event is raised in the Microsoft.Exchange.ManagedAvailability\Monitoring channel. In addition, the Microsoft-Exchange-ActiveMonitoring/MonitorResult channel shows the following error message:

ResultName: SubmissionQueueLengthMonitor

Log Name: Microsoft-Exchange-ActiveMonitoring/MonitorResult

Source: Microsoft-Exchange-ActiveMonitoring

Monitor result (Name=SubmissionQueueLengthMonitor)

<Error>Transition timeout should be in increasing order. TransitionId=1</Error>

<Exception>System.ArgumentException: Transition timeout should be in increasing order. TransitionId=1

It’s expected that there's an event in the Microsoft.Exchange.ManagedAvailability\Monitoring channel stating that the submission queue length exceeds threshold.


To work around this issue, you can use the following monitoring override:
Add-ServerMonitoringOverride -Server <servername>  -Identity HubTransport\SubmissionQueueLengthMonitor -ItemType "Monitor" -PropertyName StateTransitionsXml -PropertyValue  '<StateTransitions> <Transition ToState="Degraded" TimeoutInSeconds="0" /> <Transition ToState="Unhealthy" TimeoutInSeconds="1" /> </StateTransitions>'


To fix this issue, install one of the following updates:


Learn about the  terminology that Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.