You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The internal-downstream-health workflow currently posts daily report issues, but recurring downstream failures are not converted into durable, deduplicated follow-up work items.
Evidence
Discovery query for downstream workflow usage was rate-limited (github-search_code returned HTTP 429 for: org:elastic "elastic/ai-github-actions/.github/workflows/gh-aw-" language:yaml).
Fallback evidence from approved data in this repo:
Open report issue #1195 documents repeated failures and suggested actions, including:
repeated gemini engine termination in elastic/ai-github-actions-playground
copilot auth failure (No authentication information found)
agent-suggestionsparse_error in elastic/oblt-aw
Duplicate checks:
/tmp/previous-findings.json only contains closed periodic [agent-suggestions] records, no matching escalation item.
Issue search for downstream-health + follow-up/dedup/recurring found no existing tracker issue.
Gap
Downstream health findings are visible, but not automatically tracked to closure. Repeated incidents can reappear in daily reports without a single canonical issue to own remediation.
Proposal
Add escalation logic to downstream-health that:
fingerprints findings by (repo, workflow, normalized error signature)
creates/updates one canonical tracking issue per fingerprint
links each daily report finding to the canonical issue
suppresses duplicate issue creation within a cooldown window
Acceptance criteria
Re-running downstream-health with the same failure signature updates an existing issue instead of creating a new one.
Daily report includes links to canonical tracking issues.
New signatures still create fresh issues automatically.
Escalation behavior is covered by at least one workflow-level test fixture/sample run output.
Note
🔒 Integrity filter blocked 144 items
The following items were blocked because they don't meet the GitHub integrity level.
#1128search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#1175list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#1175search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#1067search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#700search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#1025search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#248search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#704search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#336search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#139search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#694search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#875search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#321search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#245search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#359search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#235search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
... and 128 more items
To allow these resources, lower min-integrity in your GitHub frontmatter:
The
internal-downstream-healthworkflow currently posts daily report issues, but recurring downstream failures are not converted into durable, deduplicated follow-up work items.Evidence
github-search_codereturned HTTP 429 for:org:elastic "elastic/ai-github-actions/.github/workflows/gh-aw-" language:yaml).#1195documents repeated failures and suggested actions, including:geminiengine termination inelastic/ai-github-actions-playgroundcopilotauth failure (No authentication information found)agent-suggestionsparse_errorinelastic/oblt-aw/tmp/previous-findings.jsononly contains closed periodic[agent-suggestions]records, no matching escalation item.Gap
Downstream health findings are visible, but not automatically tracked to closure. Repeated incidents can reappear in daily reports without a single canonical issue to own remediation.
Proposal
Add escalation logic to downstream-health that:
(repo, workflow, normalized error signature)Acceptance criteria
Note
🔒 Integrity filter blocked 144 items
The following items were blocked because they don't meet the GitHub integrity level.
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:What is this? | From workflow: Trigger Agent Suggestions
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.