You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🔒 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.
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.
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 Copilot using the agentic-workflows sub-agent to automatically debug and fix the workflow failure.
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/github/gh-aw-firewall/actions/runs/24593463075
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.
Workflow Failure
Workflow: Smoke Claude
Branch: copilot/optimize-claude-token-usage-again
Run: https://github.com/github/gh-aw-firewall/actions/runs/24593463075
Pull Request: #2065
🔒 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
.mdfile was edited butgh aw compilewas not run afterwards to regenerate the corresponding.lock.ymlfile. The agent is prevented from running against a stale configuration to avoid unexpected behaviour.To fix, recompile the workflow:
Then commit and push the updated
.lock.ymlfile.More ways to recompile
Using the gh-aw MCP server (if configured):
{ "tool": "compile", "arguments": { "validate": true } }Recompile all workflows at once:
Verify the result:
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:This makes it easy to spot accidental whitespace changes, encoding differences, or import path drift.
How to disable this check
Set
stale-check: falsein theon:section of your workflow frontmatter:After editing, recompile the workflow:
gh aw compileAction Required
Assign this issue to Copilot using the
agentic-workflowssub-agent to automatically debug and fix the workflow failure.Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the
agentic-workflowsprompt.agentic-workflowsprompt from.github/agents/agentic-workflows.agent.mdor https://github.com/github/gh-aw/blob/main/.github/agents/agentic-workflows.agent.mddebug the agentic workflow smoke-claude failure in https://github.com/github/gh-aw-firewall/actions/runs/24593463075Tip
Stop reporting this workflow as a failure
To stop a workflow from creating failure issues, set
report-failure-as-issue: falsein its frontmatter: