Actions Fleet Monitor — 2026-08-30

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

Fleet Health

🔴 CRITICAL: 3 🟠 DEGRADED: 2 🟡 WARNING: 2 ✅ HEALTHY: 55

pie title Workflow Status Distribution
  "CRITICAL" : 3
  "DEGRADED" : 2
  "WARNING" : 2
  "HEALTHY" : 55

⚠️ Systemic Issues

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

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

Top Failing Workflows

xychart-beta
  title "Top Failing Workflows (≥5 runs)"
  x-axis [".github-private/.github/workflows/dev-lead.yml","broodly/.github/workflows/dev-lead.yml","repo-template/.github/workflows/dev-lead.yml","bmad-bgreat-suite/.github/workflows/ci-failure-analyst.yml","repo-template/.github/workflows/pr-auto-review.yml",".github-private/.github/workflows/pr-review-trigger.yml"]
  y-axis "Failure Rate %" 0 --> 100
  bar [100,100,82,28,6,1]

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/docs-health-check.yml

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

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

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

petry-projects/bmad-bgreat-suite / .github/workflows/ci-failure-analyst.yml

petry-projects/bmad-bgreat-suite / .github/workflows/dev-lead.yml

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

petry-projects/google-app-scripts / .github/workflows/dev-lead.yml

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

petry-projects/repo-template / .github/workflows/ci.yml

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

petry-projects/repo-template / .github/workflows/pr-auto-review.yml

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: