> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Architect health

> Review rolling Workflow Architect failure telemetry and acknowledge open drift alerts.

**Architect Health** (`/analytics/architect-health`) is the administrator-only telemetry surface for
the Workflow Architect. It reports a rolling 30-day window and compares relevant counts with the
prior window.

![Architect Health (light)](https://mintcdn.com/gloo-b243725a/xyq5perq6SLByPBn/forge/images/console/analytics/architect-health-light.png?fit=max\&auto=format\&n=xyq5perq6SLByPBn\&q=85\&s=b55665a58f1f0e4ed171247c202ffca8)

Architect Health — Forge Console at `/analytics/architect-health`

## What you can do

* **Review the 30-day window**: Architect turns, error rate, tripwires and yield-mismatch incidents against the prior window.
* **Find the most frequent failures**: validator error codes and failed tools, with current and prior counts.
* **Acknowledge a drift alert** once you have recorded or begun the follow-up.

## Review the current window

The summary shows:

* Architect turns and error rate.
* Soft and hard tripwire counts.
* Yield-mismatch incidents.

The detail panels list the most frequent validator error codes and failed tools, with their current
and prior counts. The daily chart plots turn volume and tripwires across the reporting window.

## Handle a drift alert

A nightly detector adds an open alert when validator-code, failed-tool, tripwire, or yield-mismatch
counts shift materially. Read the alert's kind, subject, current and prior counts, and detection date.
Choose **Acknowledge** after you have recorded or begun the appropriate follow-up. Acknowledging the
alert removes it from the open list; it does not change the underlying telemetry or repair the
Workflow Architect.

The page does not provide conversation drill-down, operator-override rate, success rate, or median
resolution turns. Use [Workflows](https://docs.gloo.com/forge/console/production/workflows) and
[Run History](https://docs.gloo.com/forge/console/observe/run-history.md) to investigate the related workflow and platform
evidence when you have its identifiers.

## Key state to watch

* **Open drift alerts.** A nightly detector opens one when validator-code, failed-tool, tripwire or yield-mismatch counts shift materially.
* **Hard tripwires.** Count them against the prior window.
* **Access restricted.** Administrator access is required.
* **An empty panel.** No matching rows were returned for that window; it is not a substitute for checking the relevant runs.

## Related surfaces

* [Agent Performance](https://docs.gloo.com/forge/console/analytics/agent-performance): the other Agent Performance tabs.
* [Workflows](https://docs.gloo.com/forge/console/production/workflows): the workflows the Architect builds.
* [Run History](https://docs.gloo.com/forge/console/observe/run-history.md): platform evidence for a run.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.