Why a check can remain unknown
A provider may be unavailable, restrict verification, or return a temporary or ambiguous response. The explanation matters because different causes call for different handling.
Why immediate retries may not help
Repeating the same check immediately can reproduce the same conditions. Follow documented guidance and consider a later review rather than creating unnecessary work.
How to build a useful rule
Keep uncertain rows separate. Preserve their reason and checked time. Decide whether your workflow should review them, try later, or use another legitimate source of evidence.
Avoid a false sense of certainty
A report with fewer unknowns is not automatically more accurate. A service that labels uncertainty honestly may give you a more useful basis for decisions. Next: Explore the example verification report.
Why the distinction changes the workflow
A malformed address asks the user to correct input. A timeout asks the application to recover from a service condition. If both become invalid, your system can reject legitimate people for a problem they cannot fix.
Write a decision table
For each result, specify the user message, stored state, retry eligibility, and next owner. Include an unfamiliar-result fallback so future response changes do not become silent acceptance.
Review one representative record with your team. Agree on the evidence, the decision, and who owns the next step before applying the same rule to a complete list.