microsoft / microsoft/FluidFramework
[agentics] Failed runs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.9k
- Forks
- 586
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 146
Description
This issue tracks all failures from agentic workflows in this repository. Each failed workflow run creates a sub-issue linked here for organization and easy filtering.
Purpose
This parent issue helps you:
- View all workflow failures in one place by checking the sub-issues below
- Filter out failure issues from your main issue list using
no:parent-issue - Track the health of your agentic workflows over time
Sub-Issues
All individual workflow failure issues are linked as sub-issues below. Click on any sub-issue to see details about a specific failure.
Troubleshooting Failed Workflows
Using agentic-workflows Agent (Recommended)
Agent: agentic-workflows
Purpose: Debug and fix workflow failures
Instructions:
- Invoke the agent: Type
/agentin GitHub Copilot Chat and select agentic-workflows - Provide context: Tell the agent to debug the workflow failure
- Supply the workflow run URL for analysis
- The agent will:
- Analyze failure logs
- Identify root causes
- Propose specific fixes
- Validate solutions
Using gh aw CLI
You can also debug failures using the gh aw CLI:
# Download and analyze workflow logs
gh aw logs <workflow-run-url>
# Audit a specific workflow run
gh aw audit <run-id>
Manual Investigation
- Click on a sub-issue to see the failed workflow details
- Follow the workflow run link in the issue
- Review the agent job logs for error messages
- Check the workflow configuration in your repository
Resources
This issue is automatically managed by GitHub Agentic Workflows. Do not close this issue manually.
- expires on Feb 25, 2026, 4:36 AM UTC
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with one linked sub-issue and its workflow run URL, then inspect the failure using the agentic-workflows agent or gh aw logs and gh aw audit. Review the referenced workflow configuration and logs; done means the specific failed workflow has an identified cause, an appropriate fix, and a validated successful run.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100