githubnext / githubnext/gh-aw-cao

[aw] CAO Maintenance / Efficiency is missing required data

Closed
#9,123 1 comment 0 reactions 0 assignees View on GitHub
agentic-workflows
Dominant language
JavaScript
Stars
3
Forks
1
Avg merge
49m
Merged PRs (30d)
837

Description

### Workflow Failure

**Workflow:** [CAO Maintenance / Efficiency](https://github.com/githubnext/gh-aw-cao/blob/main/.github/workflows/cao-maintenance-efficiency.md)
**Branch:** main
**Run:** https://github.com/githubnext/gh-aw-cao/actions/runs/34542391335

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

**Missing Data:**
- **activity-cache and workflow run logs**: The restored activity cache directory \\$\\{RUNNER\_TEMP}/cao-activity/gh-aw-logs.jsonl \(schema-v2 run records\) is absent from this run's runner temp — the actions/cache/restore step ran but produced no cao-activity directory, indicating a cache miss with no pr
\[Content truncated due to length\]
- *Context*: Task: CAO Maintenance / Efficiency worker for package cao-maintenance, target githubnext/gh-aw-cao, correlation\_id 34542391335-2, run https://github.com/githubnext/gh-aw-cao/actions/runs/34542391335. Required: 7-day \(and comparison 7-day\) schema-v2 run rec
\[Content truncated due to length\]
- *Alternatives*: Options considered and rejected: \(1\) infer package health from cao.json policy alone — rejected, policy has no run outcome data; \(2\) use SAFE\_OUTPUT\_REPO review-item search alone without run evidence — rejected, review items alone cannot establish run succ
\[Content truncated due to length\]

### 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/githubnext/gh-aw-cao/actions/runs/34542391335
````

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 cao-maintenance-efficiency failure in https://github.com/githubnext/gh-aw-cao/actions/runs/34542391335`

> [!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 [CAO Maintenance / Efficiency](https://github.com/githubnext/gh-aw-cao/actions/runs/34542391335) · copilot · 52 AIC · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-cao+is%3Aissue+%22gh-aw-workflow-id%3A+cao-maintenance-efficiency%22&type=issues)
> - [x] expires on Sep 17, 2026, 11:39 PM UTC

Contributor guide

Open the contributing guide

Research direction

Start with .github/workflows/cao-maintenance-efficiency.md and the failed run 34542391335, then read debug.md and .github/skills/agentic-workflows/SKILL.md. Trace why the restored activity-cache directory and schema-v2 workflow logs are absent. Done means the workflow receives the required seven-day run data and completes without reporting missing data.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.