Files
agent-estate-wiki/incidents/2026-10-01-cliproxy-connection-auth-expired.md
T
Tony0410 0c4ed3350b wiki audit 2026-10-02: 2 new cron failures, cliprox/terra connection auth incident, delivery-failure semantics corrected, profile rewrite, broken wikilinks repaired
- new: incidents/2026-10-01-cliproxy-connection-auth-expired.md (HTTP 401, credential fault, cannot self-recover)
- systems/scheduled-tasks.md: 30 jobs / 27 enabled; failing 3 -> 6; streaks advanced; wiki-tree drift recorded
- systems/messaging-integrations.md: two distinct thread-failure variants (lost vs thread-less fallback)
- systems/current-profile.md: full rewrite from live config (no profiles/default/, smart-route, OmniRoute)
- current-state.md / index.md / log.md: 2026-10-02 entry
- repair: copied 5 vault-only pages referenced by index.md (ignis, nextcloud, 3 incidents) so wikilinks resolve
- include pending stocktake output: skills-index.md 2026-09-27, raw/stocktake/freshness-2026-09-2{6,7}.txt
2026-10-02 00:17:15 +08:00

2.8 KiB

title, type, status, created, updated, verified_on, confidence, tags, sources
title type status created updated verified_on confidence tags sources
OmniRoute cliprox/terra Connection Auth Expiry incident open 2026-10-02 2026-10-02 2026-10-02 high
cron
omniroute
provider
auth
incident
live-jobs-json
cron-executions-db
cron-session-cron_06a0a1c8704f_20261001_100040

OmniRoute cliprox/terra Connection Auth Expiry

Window: first failure 2026-10-01 10:00 AWST (job schedule 0 10 * * 4); still open Status: Open — not self-recovering Impact: 1 job failed outright; 2 more enabled jobs share the same model pin and are expected to fail on their next runs

Symptoms

Job 06a0a1c8704f (AI Newsletter Curation for Patrick, Thu 10:00) aborted with:

HTTP 401: [openai-compatible-chat-2ea20f63-…] All 1 connection(s) authentication expired
— please reconnect in the dashboard

Provider custom:Omniroute:20128, model cliprox/terra. The run's failure notice was delivered to forum topic 346, but no newsletter digest was produced.

Root Cause

A connection credential at the provider, not a missing or plan-gated model and not a routing error. The error names a single connection (All 1 connection(s)) whose authorisation lapsed, so the model pin itself is still valid — the credential behind it is not.

This matters because it is the one failure class from the 2026-10-01 sweep that cannot self-recover. A retired or plan-gated model stays broken until repinned; an expired connection stays broken until a human re-authenticates it in the dashboard.

Blast Radius

Three enabled jobs run cliprox/terra:

Job Name Schedule Delivery
06a0a1c8704f AI Newsletter Curation for Patrick 0 10 * * 4 telegram:-1004321904721:346
1b23c042e17d Enhanced Weekend Adventure Planner 0 8 * * 5 telegram:-1004321904721:102
79f9bb41ecf5 Weekly Review 0 18 * * 0 origin

Only 06a0a1c8704f had run by 2026-10-02; the other two are exposed on their next scheduled runs.

Fix

Re-authenticate the OmniRoute connection for cliprox/terra. Do not repin these jobs to another raw model as a first move — that treats a credential fault as a routing fault and will produce a second, different outage. If the connection cannot be restored, repin all three jobs together to a routing alias (smart-route).

Distinguish From

  • Plan-gated model (403 MODEL_NOT_IN_PLAN, job dca8482e4f76) — the upstream rejects the model by plan; no credential involved.
  • Retired model (HTTP 410, job 1a8e90ea2271) — the model no longer exists upstream.
  • Catalog-missing model (HTTP 400, jobs fad5a86979d4 / 0e753e9720fd) — the model name is absent from the provider's live catalog.