githubnext / githubnext/gh-aw-cao

[aw] SelfCare / Dashboard Performance has cache-memory miss misconfiguration

Closed
#8,637 10 comments 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:** [SelfCare / Dashboard Performance](https://github.com/githubnext/gh-aw-cao/blob/main/.github/workflows/self-care-dashboard-performance.md)
**Branch:** main
**Run:** https://github.com/githubnext/gh-aw-cao/actions/runs/34484973555

> [!WARNING]
>
> Cache Configuration Problem: cache miss detected after cache restore succeeded.
>
> The agent reported a cache miss (`missing_data` with `reason: cache_memory_miss`) after the workflow successfully restored cache-memory for this run. This likely indicates the prompt is misconfigured and the agent cannot locate the correct file path within the cache directory.
>
> This warning is shown only when a cache restore matched an existing key. Cache misses can be expected on first runs and on branches where `actions/cache` has no visible entries due to branch scoping.
>
> Review the [cache-memory configuration](https://github.github.com/gh-aw/reference/cache-memory/) and ensure the agent prompt correctly references files inside the cache directory.
>
> **File naming convention:** Cache files are stored at `/tmp/gh-aw/cache-memory/` (default) or `/tmp/gh-aw/cache-memory-{id}/` for additional caches. Use descriptive file and directory names with subdirectories for organization.
>
>

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

**Missing Tools:**
- **upload\_artifact**: Performance evidence exists at /home/runner/work/gh-aw-cao/gh-aw-cao/self-care-dashboard-performance-evidence, but the required upload\_artifact safe-output tool is not available in this environment.

Alternatives:

| Tool | Alternative |
| --- | --- |
| upload\_artifact | The evidence remains on disk for this run under self-care-dashboard-performance-evidence. |

### 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/34484973555
````

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 self-care-dashboard-performance failure in https://github.com/githubnext/gh-aw-cao/actions/runs/34484973555`

> [!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 [SelfCare / Dashboard Performance](https://github.com/githubnext/gh-aw-cao/actions/runs/34484973555) · copilot · 231.6 AIC · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-cao+is%3Aissue+%22gh-aw-workflow-id%3A+self-care-dashboard-performance%22&type=issues)
> - [x] expires on Sep 17, 2026, 2:06 PM UTC

Contributor guide

Open the contributing guide

Research direction

Start with .github/workflows/self-care-dashboard-performance.md and the failed run 34484973555. Compare the workflow's cache-memory prompt and paths with the cache-memory reference, then determine why the restored cache is reported as missing; also verify how upload_artifact is expected to be provided. Done means the workflow can locate restored cache data and handle performance evidence without the reported failures.

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
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.