Target Server not removed from loadbalancer even after failures

Hi

We have the below configuration in our target server with load balancer and health monitor enable.

As part of DR strategy have tested bringing down application of one of the target server, however even after 10 mins we could see that target server is not removed from load balancer rotation. Bringing down the application have started to give 502 when hitting the origin url. And 502 is not in the success codes of the load balancer, hence we expect the target server to be removed from rotation after max failures has been reached.

Can someone let me know where we have configured it incorrectly?

<HTTPTargetConnection>
    <Properties>
        <Property name="success.codes">1XX,2XX,3XX,4XX,500,501,505</Property>
    </Properties>
    <LoadBalancer>
        <Algorithm>RoundRobin</Algorithm>
        <Server name="target-server-1"/>
        <Server name="target-server-2"/>
        <MaxFailures>5</MaxFailures>
        <RetryEnabled>true</RetryEnabled>
    </LoadBalancer>
    <Properties/>
    <Path>/XXXXXXXX</Path>
    <HealthMonitor>
        <IsEnabled>true</IsEnabled>
        <IntervalInSec>60</IntervalInSec>
        <HTTPMonitor>
            <Request>
                <ConnectTimeoutInSec>2</ConnectTimeoutInSec>
                <SocketReadTimeoutInSec>10</SocketReadTimeoutInSec>
                <Port>443</Port>
                <Verb>GET</Verb>
                <Path>/XXXXXXXX/_status</Path>
                <Header name="TraceId">aaaa:bbbb:cccc</Header>
            </Request>
            <SuccessResponse>
                <ResponseCode>200</ResponseCode>
             </SuccessResponse>
        </HTTPMonitor>
    </HealthMonitor>
</HTTPTargetConnection>

Regards,

Venkat

1 0 89