wiki audit 2026-10-05: cliprox/terra pin settled 3/3 (Weekly Review failed 2026-10-04 18:00), failing set 6->7, streak-counter/executions.db-retention caveat
This commit is contained in:
@@ -3,18 +3,18 @@ title: OmniRoute cliprox/terra Connection Auth Expiry
|
||||
type: incident
|
||||
status: open
|
||||
created: 2026-10-02
|
||||
updated: 2026-10-03
|
||||
verified_on: 2026-10-03
|
||||
updated: 2026-10-05
|
||||
verified_on: 2026-10-05
|
||||
confidence: high
|
||||
tags: [cron, omniroute, provider, auth, incident]
|
||||
sources: [live-jobs-json, cron-executions-db, cron-session-cron_06a0a1c8704f_20261001_100040]
|
||||
sources: [live-jobs-json, cron-executions-db, cron-session-cron_06a0a1c8704f_20261001_100040, cron-session-cron_79f9bb41ecf5_20261004_180050]
|
||||
---
|
||||
|
||||
# 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:** 2 of the 3 exposed jobs have now failed on this pin; 1 remains untested
|
||||
**Status:** Open — not self-recovering; **all 3 exposed jobs now confirmed broken**
|
||||
**Impact:** 3 of 3 jobs on this pin have failed on it; no job on `cliprox/terra` has produced output since the credential lapsed
|
||||
|
||||
## Symptoms
|
||||
|
||||
@@ -66,10 +66,25 @@ That is now **2 of 3** exposed jobs confirmed broken on this pin, which retires
|
||||
doubt about a one-job fluke. Its failure notice was delivered to topic `102`, so the
|
||||
run is recorded `delivery_outcome: delivered` even though no plan was produced.
|
||||
|
||||
`79f9bb41ecf5` (**Weekly Review**, Sun 18:00) is the last untested one — its only
|
||||
`79f9bb41ecf5` (**Weekly Review**, Sun 18:00) was the last untested one — its only
|
||||
recorded run was 2026-09-27 18:00, four days *before* the connection lapsed, and it
|
||||
succeeded. Its next scheduled run is **2026-10-04 18:00**, which will confirm whether
|
||||
the expiry is tenant-wide for this model or per-connection.
|
||||
succeeded. Its next scheduled run was **2026-10-04 18:00**.
|
||||
|
||||
### Third job confirmed — 2026-10-04 18:00 · pin settled 3/3
|
||||
|
||||
`79f9bb41ecf5` ran on schedule on 2026-10-04 18:00 and failed with the *identical*
|
||||
error again:
|
||||
|
||||
```
|
||||
HTTP 401: [openai-compatible-chat-2ea20f63-…] All 1 connection(s) authentication expired
|
||||
— please reconnect in the dashboard
|
||||
```
|
||||
|
||||
That settles it: **3 of 3** jobs on `cliprox/terra` have now failed on the same
|
||||
credential fault. There is no remaining doubt about scope — it is not per-job, and it
|
||||
will not self-recover. Failure streak for `79f9bb41ecf5` is 1; no review was produced.
|
||||
The run's `delivery_outcome` is again `delivered` (the failure notice is the
|
||||
deliverable), so the execution `status` is the only honest signal.
|
||||
|
||||
Corollary worth recording: a job can be recorded as **successfully delivered while
|
||||
having failed**, because the failure notice itself is a deliverable. Read the
|
||||
|
||||
Reference in New Issue
Block a user