MoveRange requests use the coordinator-based path in shardsvr_move_range_command.cpp, where terminal failures are logged by sharding_coordinator.cpp. In the legacy path, a LockTimeout while acquiring the migration critical-section lock was logged as a warning (shardsvr_move_range_command.cpp). SERVER-136085 restored warning severity for that case.

This investigation should identify whether other MoveRange errors changed severity with the coordinator-based implementation and recommend whether any of them needs correction, as in the case of LockTimeout, based on whether it represents an expected, retryable condition or an unexpected failure.