router_transactions_metrics.js uses a fail point that hangs find commands to ensure a transaction is actively running when it checks transaction metrics in serverStatus. It uses currentOp to wait for exactly one thread to reach the fail point, but as of SERVER-46395, the range deleter runs a find that can trigger the fail point at the same time as the transaction, causing the test to hang. The fail point should instead use the "nss" parameter so only the transaction find will trigger the fail point.