[aw] Triage Panel has stale lock file

Nobody has claimed this yet.

Workflow Failure

Workflow: Triage Panel
Branch: main
Run: https://github.com/microsoft/apm/actions/runs/35221460885

[!WARNING]
Lock File Out of Sync: The workflow could not start because its compiled lock file no longer matches the source markdown.

This means the workflow's .md file was edited but gh aw compile was not run afterwards to regenerate the corresponding .lock.yml file. The agent is prevented from running against a stale configuration to avoid unexpected behaviour.

To fix, recompile the workflow:

gh aw compile

Then commit and push the updated .lock.yml file.

More ways to recompile

Using the gh-aw MCP server (if configured):

{ "tool": "compile", "arguments": { "validate": true } }

Recompile all workflows at once:

gh aw compile --all

Verify the result:

gh aw compile --validate

How to investigate the mismatch

The workflow run logs contain a verbose debug pass that shows exactly what was hashed. Search the Check workflow lock file step logs for lines starting with [hash-debug] to see:

The raw frontmatter text that was used as input
Any imported files that were included in the hash
The canonical JSON that was fed to SHA-256
The resulting hash value

This makes it easy to spot accidental whitespace changes, encoding differences, or import path drift.

This mismatch can also happen on a fresh install (even without any manual edits) if gh aw add <path>@<ref> could not resolve the ref to an exact commit SHA during installation. In that case, rerun the add command with an exact SHA (or retry when API/rate-limit conditions recover), then recompile:

gh aw add <path>@<exact-sha>
gh aw compile

How to disable this check

[!CAUTION]
Disabling this check means the agent can run against an out-of-date compiled workflow. Only disable it if you have an alternative mechanism to keep lock files in sync.

Set stale-check: false in the on: section of your workflow frontmatter:

on:
  issues:
    types: [opened]
  stale-check: false

After editing, recompile the workflow: gh aw compile

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/microsoft/apm/actions/runs/35221460885

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 https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.md
Type debug the agentic workflow triage-panel failure in https://github.com/microsoft/apm/actions/runs/35221460885

[!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 Triage Panel · ◷

expires on Sep 24, 2026, 12:32 PM UTC

Start with .github/workflows/triage-panel.md and the failed run's Check workflow lock file logs, including the [hash-debug] lines. Run gh aw compile, then gh aw compile --validate to verify the generated lock file matches the source. Done means committing and pushing the updated corresponding .lock.yml file.

Written by the indexing model from the issue text.

Description

Workflow Failure

Action Required

Contributor guide

First steps

Research direction

Assessment

[aw] Triage Panel has stale lock file

Description

Workflow Failure

Action Required

Contributor guide

First steps

Research direction

Assessment

Get new issues in your inbox