RouteLink Server Actions on Hash Failure
When the RouteLink Server encounters a failed hash, it begins a traversal of the database to determine the failed TFNs. Rather than traversing tens of millions of TFNs linearly, a more efficient algorithm is employed, where the RouteLink Server requests hashes of more specific, partial, CRNs. For example, the server requests the hash of a partial CRN of "8000", "8001", ... "8009" to narrow down its search. The RouteLink Client does not have to determine where the failure occurs, that is the responsibility of the RouteLink Server. The RouteLink Client only needs to be prepared to respond with any partial CRN hashes requested by the RouteLink Server. The partial CRN could have any length from 1 to 10 digits.
Disclaimer: Any images in this article are intended to be used as a guide for educational purposes only and they may differ slightly from the Production Environment.
The following permanent error message is returned if the server finds audit issues with more than 100 TFNs per NPA audit for the client:
"Audit failed- too many errors"