tinyagents harness: OpenHuman HTTP 401 Invalid token affecting 32 users

[senamakel]

Sentry: https://sentry.tinyhumans.ai/organizations/tinyhumans/issues/25306/ (TAURI-RUST-PRN)
Impact: 350 events · 32 users · error
Seen: first 2026-07-15 · last 2026-07-23
Release / env: openhuman@0.63.1+e3a7f521787d / production

Exception: tinyagents harness run failed: model error: OpenHuman returned HTTP 401: {"success":false,"error":"Invalid token","errorCode":"UNAUTHORIZED"}
Culprit: (none)

Analysis: The backend is rejecting inference requests with 401 Invalid Token. This may indicate expired/revoked auth tokens across multiple users. Could be a backend-side token validation issue or a client-side token refresh gap.

Source: Sentry TAURI-RUST-PRN.

[YellowSnnowmann]

Closing as fixed.

PR #5171 (merged 2026-07-24, commit 55d3ab5cc) wired maybe_publish_session_expired() on both the invoke path (line 494) and stream path (line 518) in src/openhuman/inference/provider/openhuman_backend_model.rs. A 401/403 from the OpenHuman provider now publishes DomainEvent::SessionExpired, triggering re-auth rather than leaving the user in a broken inference state. maybe_publish_local_session_expiry() at line 138 also catches pre-flight expired JWTs before any doomed request is sent.

The issue was last seen in Sentry on 2026-07-23 — the day before the fix landed.