github-aw-troubleshooting

Troubleshoot GitHub Agentic Workflow failures by auditing run artifacts like missing_tools and safe_outputs.jsonl. Analyze execution logs to isolate root causes such as missing tool declarations or safe-output configuration issues, apply frontmatter and prompt fixes, then validate the changes by compiling with `gh aw compile`.

Safe-output configuration issues in gh-aw workflows stem from misconfigured frontmatter or prompt definitions that fail validation. Analyze prior run logs and safe_outputs.jsonl artifacts to detect these misconfigurations, apply the necessary frontmatter corrections, and confirm the workflow compiles successfully using `gh aw compile --strict`.

Yes, you can debug GitHub Enterprise Cloud agentic workflows with data residency requirements by configuring the correct `api-target` and `GH_HOST` environment variables. This ensures your workflow authentication and execution align with your specific GHE Cloud instance during the troubleshooting and log forensics process.

Find the root cause of timeouts and firewall denials in agentic workflows by performing log forensics on prior workflow execution logs. Isolate token usage patterns and performance bottlenecks from run artifacts, adjust your prompt or tool configurations accordingly, and verify the remediation by compiling the workflow.

Use `gh aw compile --strict` during workflow debugging when you need rigorous validation after applying frontmatter, prompt, or tool configuration changes. Strict mode compilation ensures your agentic workflow meets all safe-output and tool auditing requirements before executing the next run.