wiki audit 2026-10-03: cliprox second job confirmed (2/3), work-mailbox incident page, streak recount, skills-index 341->344
This commit is contained in:
@@ -3,8 +3,8 @@ title: OmniRoute cliprox/terra Connection Auth Expiry
|
||||
type: incident
|
||||
status: open
|
||||
created: 2026-10-02
|
||||
updated: 2026-10-02
|
||||
verified_on: 2026-10-02
|
||||
updated: 2026-10-03
|
||||
verified_on: 2026-10-03
|
||||
confidence: high
|
||||
tags: [cron, omniroute, provider, auth, incident]
|
||||
sources: [live-jobs-json, cron-executions-db, cron-session-cron_06a0a1c8704f_20261001_100040]
|
||||
@@ -14,7 +14,7 @@ sources: [live-jobs-json, cron-executions-db, cron-session-cron_06a0a1c8704f_202
|
||||
|
||||
**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
|
||||
**Impact:** 2 of the 3 exposed jobs have now failed on this pin; 1 remains untested
|
||||
|
||||
## Symptoms
|
||||
|
||||
@@ -49,9 +49,32 @@ Three enabled jobs run `cliprox/terra`:
|
||||
| `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
|
||||
Only `06a0a1c8704f` had run by 2026-10-02; the other two were exposed on their next
|
||||
scheduled runs.
|
||||
|
||||
### Second job confirmed — 2026-10-02 08:00
|
||||
|
||||
`1b23c042e17d` (**Enhanced Weekend Adventure Planner**, Fri 08:00) failed on schedule
|
||||
with the *identical* error:
|
||||
|
||||
```
|
||||
HTTP 401: [openai-compatible-chat-2ea20f63-…] All 1 connection(s) authentication expired
|
||||
— please reconnect in the dashboard
|
||||
```
|
||||
|
||||
That is now **2 of 3** exposed jobs confirmed broken on this pin, which retires any
|
||||
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
|
||||
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.
|
||||
|
||||
Corollary worth recording: a job can be recorded as **successfully delivered while
|
||||
having failed**, because the failure notice itself is a deliverable. Read the
|
||||
execution `status`, not the delivery outcome, when judging whether a job worked.
|
||||
|
||||
## Fix
|
||||
|
||||
Re-authenticate the OmniRoute connection for `cliprox/terra`. Do **not** repin these jobs
|
||||
|
||||
Reference in New Issue
Block a user