elastic / elastic/docs-content

[aw] Gh Aw Issue Triage reported incomplete result

Open
#7,118 0 comments 0 reactions 0 assignees View on GitHub
agentic-workflows
Dominant language
No language data
Stars
47
Forks
261
Avg merge
3d 12h
Merged PRs (30d)
116

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/28227413032
**Pull Request:** [#5583](https://github.com/elastic/docs-content/pull/5583)

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

**Reasons:**
- Issue #7117 is filtered by the integrity policy — the MCP server blocked access to the issue body and title (integrity below "approved"). Without the issue content, triage cannot be performed.

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

The failed workflow run is at https://github.com/elastic/docs-content/actions/runs/28227413032
````

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/28227413032`

> [!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/28227413032) · 23.8 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 3, 2026, 8:51 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 28227413032, then read the gh-aw debug.md guidance and the agentic-workflows skill at .github/skills/agentic-workflows/SKILL.md. Confirm why the workflow could not access issue #7117 and verify that a rerun can complete triage rather than emit report_incomplete.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.