# Model “Couldn’t Check” as a Different State From Zero Results

> Source: <https://dev.to/jeremynwokorie/model-couldnt-check-as-a-different-state-from-zero-results-4jie>
> Published: 2026-11-22 02:08:34+00:00

**Recommendation:** Represent queue status as checked, stale, or unavailable instead of defaulting to zero, and preserve the last successful check timestamp so users can tell a failed refresh from a genuine empty result.
More in the playbook "Running AI in production": <https://wpnews.pro/playbooks/production-ops>

*From Primetime Home Health Services. Prepared with AI drafting assistance. This is a synthetic TypeScript example for a generic staff queue, not a live PTHHS screen or a decision about care, pay, or eligibility.*

A dashboard that says “0 items” is making a claim: the last check succeeded and found none. If the request failed, a zero is the wrong default. The difference matters when an office is deciding whether anyone still needs to review the queue.

```
type Queue =
  | { kind: "checked"; count: number; at: string }
  | { kind: "stale"; at: string }
  | { kind: "unavailable" };

function message(s: Queue) {
  switch (s.kind) {
    case "checked":
      return `${s.count} items need review. Checked at ${s.at}.`;
    case "stale":
      return `Refresh failed. Last checked at ${s.at}; the earlier count may have changed.`;
    case "unavailable":
      return "Couldn’t check the list. Try refreshing.";
  }
}
```

Here, `at` stands for the last completed check for this same view, formatted clearly for the reader. A new network attempt should not overwrite it with a fresh clock time. Treat a partial response as unavailable for this total rather than reporting it as a complete check. Do not carry a result across a change in the source, active view or session.

Keep the status readable without color. For an in-place update, test that assistive technology can announce it without pulling focus from the person’s current task. See [W3C’s status-message guidance](https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html). Test with invented values, not office records.

[Read the exact PTHHS original, Why Healthcare AI Should Learn From Mistakes](https://pthhs.net/articles/why-healthcare-ai-should-learn-from-mistakes), for the administrative context. Published from [Jeremy Nwokorie’s](https://www.linkedin.com/in/jeremynwokorie/) account on behalf of Primetime Home Health Services.
