If at some point before query execution we encounter a delay that exceeds the maxTimeMs set on a query, the query won't be killed; instead the query will be allowed to execute to completion & we may even get a slow-query log after.

Note that if the query was issued on a sharded cluster, the router will correctly detect the timeout/ cancel the operation; however, the mongod will continue to execute the query past the timeout.