You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
⚠️ Missing Data Reported: The agent reported missing data during execution.
Missing Data:
GraphQL node_id fields for issue comments (format: IC_kwDO...): hide_comment requires GraphQL node IDs, but github-issue_read get_comments only returned numeric REST API IDs
Context: Comments 4641462382 (resolved investigation, P2) and 4645552381 (daily overview >7d, P1) qualify for hiding on issue 🏥 Repository Health Dashboard #695
Alternatives: Query the GraphQL API directly (POST /graphql) to retrieve IssueComment.id node IDs for these two comments
Action Required
Assign this issue to an agent to debug and fix the issue.
Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md
The failed workflow run is at https://github.com/dotnet/skills/actions/runs/27532805613
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.
Workflow Failure
Workflow: DevOps Health — Groom Dashboard
Branch: main
Run: https://github.com/dotnet/skills/actions/runs/27532805613
Missing Data:
Action Required
Assign this issue to an agent to debug and fix the issue.
Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the
agentic-workflowsprompt.agentic-workflowsskill from.github/skills/agentic-workflows/SKILL.mdor https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.mddebug the agentic workflow devops-health-groom failure in https://github.com/dotnet/skills/actions/runs/27532805613Tip
Stop reporting this workflow as a failure
To stop a workflow from creating failure issues, set
report-failure-as-issue: falsein its frontmatter: