elastic / elastic/docs-content

[aw] Gh Aw Issue Triage is missing required data

Open
#7,215 1 comment 0 reactions 0 assignees View on GitHub
agentic-workflows
Dominant language
No language data
Stars
47
Forks
261
Avg merge
3d 21h
Merged PRs (30d)
141

Description

### Workflow Failure

**Workflow:** [Gh Aw Issue Triage](https://github.com/elastic/docs-content/blob/main/.github/workflows/gh-aw-issue-triage.md)
**Branch:** main
**Run:** https://github.com/elastic/docs-content/actions/runs/28775964411
**Pull Request:** [#5583](https://github.com/elastic/docs-content/pull/5583)

> [!WARNING]
> **Missing Data Reported**: The agent reported missing data during execution.

**Missing Data:**
- **Issue #7204 body, title, and labels**: The GitHub MCP server filters issue #7204 with an integrity policy error: "Resource has lower integrity than agent requires." Without the issue content, classification, section validation, and body rewrite cannot proceed.
- *Context*: MCP error: "issue:elastic/docs-content#7204 exists but is not accessible — filtered by integrity policy \(Resource 'issue:elastic/docs-content#7204' has lower integrity than agent requires. The agent cannot read data with integrity below 'approved'."
- *Alternatives*: A team member can manually triage the issue, or the integrity policy for this issue may need to be raised to 'approved' before the triage workflow can process it.

### 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/elastic/docs-content/actions/runs/28775964411
````

Manually invoke the agent

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

- Start your agent
- Load the `agentic-workflows` skill from `.github/skills/agentic-workflows/SKILL.md` or
- Type `debug the agentic workflow gh-aw-issue-triage failure in https://github.com/elastic/docs-content/actions/runs/28775964411`

> [!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:
> ```yaml
> safe-outputs:
> report-failure-as-issue: false
> ```
>
>

> Generated from [Gh Aw Issue Triage](https://github.com/elastic/docs-content/actions/runs/28775964411) · 16.5 AIC · [◷](https://github.com/search?q=repo%3Aelastic%2Fdocs-content+is%3Aissue+%22gh-aw-workflow-id%3A+gh-aw-issue-triage%22&type=issues)
> - [x] expires on Jul 13, 2026, 7:50 AM UTC

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with .github/workflows/gh-aw-issue-triage.md and the failed run 28775964411; use the referenced debug.md and agentic-workflows skill to trace why issue #7204 is filtered by the integrity policy. Done means the workflow can access the required issue data and complete classification, section validation, and body rewriting.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.