Skip to content

[deep-report] Reduce Issue Monster execution drift and add deterministic fallback for MCP read failures #22921

@github-actions

Description

@github-actions

Description

Issue Monster shows high execution drift (0 to 14 turns across recent successful runs) and 2 recent missing_data events tied to MCP issue-read failures. Add deterministic fallback behavior when issue metadata cannot be fetched (bounded retry + explicit skip classification), and cap exploratory loops to keep run shape consistent.

Expected Impact

  • Lower token variance and runtime volatility
  • Fewer partial/indeterminate outcomes when MCP data is transiently unavailable
  • More predictable assignment/comment behavior across runs

Suggested Agent

copilot (issue workflow optimization + guardrails)

Estimated Effort

Medium (1-4 hours)

Data Source

DeepReport analysis run (workflow run §23549309910); Issue Monster logs summary over last 8 runs: 1,756,626 tokens, 46 turns total, and 2 missing-data events.

Note

🔒 Integrity filter blocked 7 items

The following items were blocked because they don't meet the GitHub integrity level.

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by DeepReport - Intelligence Gathering Agent ·

  • expires on Mar 27, 2026, 3:47 PM UTC

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions