Standing alarm — one per breach episode. This issue is maintained by dataSyncWatchdog.mjs:
the body is refreshed on every breach evaluation and the issue closes automatically on recovery.
Streak: 30 consecutive failures on dev.
Last success: none in the last 30 completed runs.
Latest failure: run 34185767654 [QUARANTINED_URL: github.com].
Corpus facets (committed dev; a green pipeline cannot attest to this backlog):
| facet |
last commit on dev |
age |
status |
issues |
2026-08-26T19:33:00Z |
297.2h |
STALE |
pulls |
2026-08-26T16:39:44Z |
300.1h |
STALE |
discussions |
2026-08-26T15:12:45Z |
301.6h |
STALE |
| Breach reasons: |
|
|
|
- 30 consecutive failures (threshold 3)
- no successful run visible in the last 30 completed runs
- corpus facet
issues is 297.2h old (threshold 48h)
- corpus facet
pulls is 300.1h old (threshold 48h)
- corpus facet
discussions is 301.6h old (threshold 48h)
Breached axes: runs are failing on schedule (30 consecutive); and the committed corpus is frozen (issues, pulls, discussions). The two are measured separately and neither implies the other.
Root-cause work (if any) is tracked elsewhere; this issue only carries the alarm.
Standing alarm — one per breach episode. This issue is maintained by
dataSyncWatchdog.mjs: the body is refreshed on every breach evaluation and the issue closes automatically on recovery. Streak: 30 consecutive failures ondev. Last success: none in the last 30 completed runs. Latest failure: run 34185767654 [QUARANTINED_URL: github.com]. Corpus facets (committeddev; a green pipeline cannot attest to this backlog):devissuespullsdiscussionsissuesis 297.2h old (threshold 48h)pullsis 300.1h old (threshold 48h)discussionsis 301.6h old (threshold 48h) Breached axes: runs are failing on schedule (30 consecutive); and the committed corpus is frozen (issues,pulls,discussions). The two are measured separately and neither implies the other. Root-cause work (if any) is tracked elsewhere; this issue only carries the alarm.