microsoft / microsoft/FluidFramework

[agentics] Failed runs

Open
#26,472 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

agentic-workflows
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:

  1. Invoke the agent: Type /agent in GitHub Copilot Chat and select agentic-workflows
  2. Provide context: Tell the agent to debug the workflow failure
  3. Supply the workflow run URL for analysis
  4. 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
  1. Click on a sub-issue to see the failed workflow details
  2. Follow the workflow run link in the issue
  3. Review the agent job logs for error messages
  4. 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.