We refined the checks used to evaluate the Arizona indexing pipeline and the application services that publish its results. Separating source access, processing, storage, and public rendering makes it easier to identify where an interruption occurs instead of treating every failure as the same problem.
The layers being checked
A usable public page depends on several connected stages. A source must be reachable, returned material must be readable, the application must be able to process the available fields, and the final route must render correctly. The refined health checks consider those stages independently.
- Source availability asks whether expected public material can be reached.
- Processing health asks whether returned information can be interpreted without an unexpected structural error.
- Record readiness asks whether enough identity and event context exists for publication.
- Application health asks whether search, county, record, and supporting routes respond as expected.
Why one status is not enough
A website can be online while one source is temporarily unavailable. A source can respond while returning an empty or changed format. A record can be stored while still lacking the context required for sitemap inclusion. Separating these states makes maintenance decisions more precise.
A passing application check does not mean every Arizona county or agency published new information at the same time.
How this affects public pages
Records continue to be evaluated against publication requirements before they are treated as normal indexable destinations. Public routes are checked for usable responses, while protected operational information remains restricted rather than exposed as a public status feed.
Visitors should see clearer separation between a working application and differences in county coverage. When an official source has not updated, Azrested cannot manufacture a newer record or infer the reason for the delay.
Operational response
When a check identifies an interruption, the affected stage can be reviewed without assuming that unrelated parts of the application have failed. This narrows troubleshooting and supports safer recovery on a system that depends on external public sources.
What visitors should do
Use Azrested to discover available pages and identify the county, agency, date, or record number connected to a result. For current custody, charges, or case outcomes, verify those clues with the original public office. Site-wide changes and meaningful availability notes will continue to be documented in the Site Updates archive.