Agent Availability Checks now let you select the HTTP response codes that are eligible for response-field evaluation.

Non-eligible responses—including `400`, `404`, and server errors by default—now make the route unavailable instead of allowing the call through without evaluating the response.

Timeouts, network errors, and lookup errors also fail closed.

The configuration test shows the returned HTTP status, whether that status is eligible, and whether the call would be blocked. Eligible responses are still evaluated against the configured response mapping.

Open Targets/RTBs, then create or edit a Target or outbound RTB and enable Agent Availability Check.

Under Eligible HTTP status codes, select the responses your availability endpoint uses for a parseable result. The default eligible responses are successful HTTP statuses.

Configure the response-field mapping that determines availability for eligible responses.

Select Test Configuration to review the returned status, status eligibility, mapped result, and whether the route would be blocked before saving.

Calls no longer route by default when the availability endpoint returns an unexpected error response or cannot be reached.

Customers whose endpoints intentionally use a nonstandard response code can explicitly allow that code and continue evaluating its response body.

Call Life records the HTTP status for passed and failed availability checks, making routing decisions easier to diagnose.