[oblt-aw][agent-suggestions] Agent suggestions - 2026-04-23

[github-actions]

Agent Suggestions

Date: 2026-04-23
Expires: 24h

1. gh-aw-reliability-triage

Trigger: Daily schedule + workflow_dispatch (optional issues: opened for [aw] ... failed)

Purpose: Build a reliability triage layer for agentic workflows that clusters repetitive failure issues (for example No Safe Outputs Generated and engine startup crashes), deduplicates per-run noise, and produces a single prioritized triage report with grouped run links and recommended owner/actions.

Proposed safe outputs: create-issue (single digest), add-comment (update existing digest), noop (when no actionable clusters)

Current pain points and supporting evidence:

• elastic/oblt-actions currently accumulates separate failure issues per workflow run, e.g.:
  • [aw] Agent Suggestions failed #856 ([aw] Agent Suggestions failed)
  • [aw] Docs Patrol failed #894 ([aw] Docs Patrol failed)
  • [aw] Dependency Review failed #898 ([aw] Dependency Review failed)
• The repo already has a dedicated no-op tracker, but not a failure-clustering workflow:
  • [aw] No-Op Runs #528 ([aw] No-Op Runs)
• The same failure pattern appears in downstream consumers, indicating a cross-repo reliability signal gap:
  • [aw] Issue Triage failed elastic-agent#13576 ([aw] Issue Triage failed)
  • [aw] Docs Patrol failed elastic-agent#13579 ([aw] Docs Patrol failed)
  • [aw] Text Auditor failed elastic-agent#13641 ([aw] Text Auditor failed, includes engine termination evidence)

Why existing workflows do not fully cover this gap:

• oblt-aw.yml in this repo is an ingress/forwarding entrypoint, not a reliability analyzer.
• Existing per-run failure issues are event-level alerts, not deduplicated triage.
• Existing suggestion issue Build 7 for 8.4 with status FAILURE elastic-agent#877 focuses on downstream workflow adoption/configuration drift, not runtime reliability clustering:
  • [oblt-aw][agent-suggestions] Agent suggestions - 2026-04-05 #877

Expected benefits:

• Engineering productivity: Maintainers review one prioritized digest instead of many near-duplicate failure issues.
• Review quality: Grouping by failure signature (safe-output failures vs engine failures) improves root-cause routing.
• Cycle time: Faster identification of recurring breakages across repos/workflows.
• Risk reduction: Early detection of systemic workflow reliability regressions before they create prolonged noise.

Potential trade-offs and rollout considerations:

• Needs conservative grouping thresholds to avoid false clusters.
• Should start report-only (no auto-closing or auto-label churn) for 1–2 weeks.
• Should enforce strict duplicate suppression (single open digest per window/workflow family).
• Consider opt-in repo allowlist first, then expand after signal quality is validated.

Duplicate Checks

• Open agent/workflow/automation issues reviewed: [oblt-aw][agent-suggestions] Agent suggestions - 2026-04-05 #877, [aw] Agent Suggestions failed #856, [aw] No-Op Runs #528, [aw] Docs Patrol failed #894, [aw] Dependency Review failed #898
• Open PRs with workflow/agent context reviewed: docs: Documentation analysis and improvement #914, docs: Documentation analysis and improvement #910, fix: use title substring match when correlating flaky tests with GitHub issues #905

Downstream Signals

• elastic/elastic-agent: [aw] Issue Triage failed elastic-agent#13576, [aw] Docs Patrol failed elastic-agent#13579, [aw] Text Auditor failed elastic-agent#13641
• elastic/oblt-aw active workflow expansion context: Add generic issue-fixer workflow path with comment-based ingress routing and dashboard gating oblt-aw#708

Suggested Next Steps

• Pilot gh-aw-reliability-triage in report-only mode with one daily digest and no automatic remediation.
• Define clustering keys (workflow_id, error class, run context) and minimum-repeat threshold.
• Measure duplicate reduction and time-to-triage before enabling broader rollout.

Note

🔒 Integrity filter blocked 70 items

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

• [oblt-aw] Control Plane Dashboard #526 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #464 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #471 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #526 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #50223 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #50286 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #50252 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #707 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #114 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #13367 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #13752 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #1726 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #13337 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #6154 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #13728 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #706 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• ... and 54 more items

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

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

---

What is this? | From workflow: Observability Agentic Workflow Entrypoint

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

• expires on Apr 30, 2026, 6:48 AM UTC