Skip to content

[aw] Daily Documentation Healer reported incomplete result #60942

Description

@github-actions

Workflow Failure

Workflow: Daily Documentation Healer
Branch: main
Run: https://github.com/github/gh-aw/actions/runs/34909933944

Warning

Credential Authentication Failed: The firewall audit log detected authentication rejections (HTTP 401/403) from AI provider APIs. The following provider credentials appear to be missing, expired, or invalid:

  • Anthropic Claude (ANTHROPIC_API_KEY)

To resolve this:

  1. Verify that the required API keys are configured as repository secrets
  2. Confirm the secrets have not expired and are still valid
  3. Check that the secret names in your workflow frontmatter match the configured repository secrets

For details on configuring engine credentials, see: Engine Reference

Warning

Task Could Not Be Completed: The agent reported that the task could not be performed due to an infrastructure or tool failure.

Reasons:

  • GitHub MCP server blocks all issue-listing/searching in this session due to an integrity policy, making Step 1 of the Daily Documentation Healer workflow impossible.

    Attempted repo:github/gh-aw is:issue is:closed label:documentation closed:>=2026-09-07 via both mcp__github__search_issues and mcp__github__list_issues (with and without date/label filters). Every call returned an empty result set with all matching items removed by an 'integrity policy', e.g.: Resource 'issue:[aw] Daily Documentation Healer reported incomplete result #60942' has lower integrity than agent requires. The agent cannot read data with integrity below 'approved'. This occurred for every list/search_issues call tried (labeled and unlabeled, dated and undated), including a plain state=OPEN listing with no filters.

By contrast, mcp__github__issue_read and mcp__github__pull_request_read succeeded for a specific already-known number (e.g. PR/issue #60931), and mcp__github__list_commits / mcp__github__list_pull_requests also returned data normally. So the restriction is specific to bulk issue discovery (list_issues / search_issues), not to reading a single already-identified issue or to PR/commit data.

This blocks Step 1 of the workflow (Identify Recently Closed Documentation Issues), which requires enumerating documentation-labeled closed issues from the last 7 days. Without that enumeration there is no way to discover candidate issue numbers to individually verify with issue_read, so Steps 2-6 (cross-referencing with code changes, classifying content vs. site-build/UI, fixing gaps, and proposing DDUw improvements) cannot proceed on real data. I am not fabricating issue numbers or guessing at gaps to work around this restriction.

Suggested next step: re-run once the GitHub MCP server's integrity/approval gate for issue search results is lifted, or provide an alternate discovery path (e.g. a webhook/log export of recently closed documentation issues) to this workflow.

This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.

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://github.com/ghraw/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/github/gh-aw/actions/runs/34909933944
Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

Tip

Stop reporting this workflow as a failure

To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:

safe-outputs:
  report-failure-as-issue: false

Generated from Daily Documentation Healer · claude · 72.9 AIC · ◷

  • expires on Sep 15, 2026, 11:50 AM UTC

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions