Skip to content

Workflow Health Dashboard — 2026-03-21 | Score: 74/100 ↑8 #22108

Closed as not planned

Description

@github-actions

Overview

Strong recovery this run — both P0/P1 workflows that were failing are now healthy. Overall health score reached 74/100 (↑8 from 66 last run). All 176 workflows have corresponding lock files.

Summary

Metric Value
Total workflows 176
Healthy 163+ (~93%)
Warning (stale locks) 13
Critical (P0) 0 ✅
Missing lock files 0 ✅

Recoveries This Run 🎉

Issue Triage Agent → RECOVERED ✅

Smoke Gemini → RECOVERED ✅

Warnings ⚠️

13 Stale Lock Files (P2)

Lock files are older than their source .md files — needs make recompile:

View 13 stale workflows
Workflow Status
agent-performance-analyzer stale lock
bot-detection stale lock
ci-doctor stale lock
daily-doc-updater stale lock
daily-security-red-team stale lock
daily-testify-uber-super-expert stale lock
delight stale lock
duplicate-code-detector stale lock
mcp-inspector stale lock
python-data-charts stale lock
smoke-copilot stale lock
ubuntu-image-analyzer stale lock
workflow-normalizer stale lock

Fix: Run make recompile to regenerate all lock files from source markdown.

Known Pre-existing Issues (P2)

  • Contribution Check: safe_outputs failure on schedule runs — pr-filter-results.json missing in schedule context. Agent logic is healthy; issue is infrastructure-level.
  • AI Moderator: ~17% failure rate due to race condition on closed PRs during branch checkout.

Healthy Workflows ✅

All critical operational workflows are running normally:

Trends

Metric This Run Previous Change
Health Score 74/100 66/100 ↑8
P0 Critical 0 1 ✅ resolved
P1 High 0 1 ✅ resolved
Stale Locks 13 14 ↓1
Total Workflows 176 175 ↑1

Actions Taken This Run

  • ✅ Confirmed Issue Triage Agent recovery (P0→Healthy)
  • ✅ Confirmed Smoke Gemini recovery (P1→Healthy)
  • ✅ Updated shared repo memory with current health state
  • ✅ Trimmed old metrics files to maintain memory size limits
  • ℹ️ 13 stale lock files noted (P2, no issue created — existing tracking)

References: §23374688097

Note

🔒 Integrity filtering filtered 1 item

Integrity filtering activated and filtered the following item during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.

  • issue:#unknown (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)

Generated by Workflow Health Manager - Meta-Orchestrator · ◷

  • expires on Mar 22, 2026, 7:27 AM UTC

Activity

  1. github-actions commented on Mar 22, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-03-22T07:27:16.032Z.

    Closed by Workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions