Actions Fleet Monitor — 2026-08-24

Org: petry-projects | Lookback: 1 day(s) | Repos: 12 | Workflows: 325

Fleet Health

🔴 CRITICAL: 5 🟠 DEGRADED: 0 🟡 WARNING: 0 ✅ HEALTHY: 42

pie title Workflow Status Distribution
  "CRITICAL" : 5
  "HEALTHY" : 42

⚠️ Systemic Issues

These workflow files are failing across multiple repos — fix the shared definition:

• .github/workflows/dev-lead.yml — failing in 3 repos

Top Failing Workflows

xychart-beta
  title "Top Failing Workflows (≥5 runs)"
  x-axis [".github/.github/workflows/canary-rollout.yml",".github/.github/workflows/dev-lead.yml",".github-private/.github/workflows/dev-lead.yml","broodly/.github/workflows/dev-lead.yml",".github-private/.github/workflows/pr-review-trigger.yml"]
  y-axis "Failure Rate %" 0 --> 100
  bar [100,86,85,85,59]

Per-Repo Summary

Fleet Detail

Failed Runs

petry-projects/.github / .github/workflows/canary-rollout.yml

petry-projects/.github / .github/workflows/dev-lead.yml

petry-projects/.github-private / .github/workflows/daily-pr-review-health.yml

petry-projects/.github-private / .github/workflows/dev-lead.yml

petry-projects/.github-private / .github/workflows/pr-review-trigger.yml

petry-projects/TalkTerm / .github/workflows/apply-repo-settings.yml

petry-projects/broodly / .github/workflows/dev-lead.yml

petry-projects/markets / .github/workflows/apply-repo-settings.yml

Dev-Lead Timeouts (walls)

Stage timeouts (reason=timeout) that escalate to a human, broken out from generic engine-error, over the window.

Per-repo rows list only repos with >=1 dev-lead marker in the window; the Total runs fleet total (and the rate denominator) include all dev-lead runs fleet-wide, incl. all-success repos with no markers.

Timeout rate (reason=timeout / total dev-lead runs fleet-wide — prevalence over all runs, not just failures): 0% (0 / 86)

Schedule Reliability

Expected cron ticks vs. actual schedule-triggered runs per scheduled workflow over the window. A cron that silently stopped firing shows as STALLED even when its last run "succeeded" — so a stalled backlog stops hiding behind a green check.

Scheduled runs are best-effort — GitHub may delay or drop ticks under load and only schedules crons on the default branch. A tolerance of 1 tick(s) is applied so a late-but-present run is not scored as a miss, and only schedule-event runs are counted (workflow_dispatch / push / repository_dispatch excluded). Run queries are capped at 1000 results per window, so very high-volume workflows may under-report actual runs.

Initiative-planner stub coverage & drift

Canonical template SHA: d4af6cd · enrolled repos (stub present): 12

✅ ALIGNED: 0 🔴 DRIFTED: 12 ⬜ MISSING (not enrolled): 0

These enrolled repos have drifted from the canonical stub — re-sync them:

Initiative-driver stub coverage & drift

Canonical template SHA: b25ee1e · enrolled repos (stub present): 12

✅ ALIGNED: 9 🔴 DRIFTED: 3 ⬜ MISSING (not enrolled): 0

These enrolled repos have drifted from the canonical stub — re-sync them: