Skip to content

⚠️ Daily News - Intermittent Failures (40% Success Rate) #10193

Description

@github-actions

Daily News - Intermittent Workflow Failures

Status Summary

Priority: P2 - HIGH
Success Rate: 40% (4 success / 6 failures in last 10 runs)
Health Score: 40/100 ⚠️
Impact: Daily digest delivery inconsistent, users missing repository updates

Failure Pattern

Recent Runs (Intermittent)

Pattern: 6 failures in last 10 runs, intermittent (not consecutive)

Impact Assessment

User Impact

  • Daily Digest: Users not receiving daily repository activity summaries
  • Visibility: Missing updates on issues, PRs, discussions, and workflow runs
  • Engagement: Reduced team awareness of repository activity

Scheduling Impact

  • Trigger: Weekday schedule (Mon-Fri at 9am UTC)
  • Coverage: Business days only (Sat-Sun excluded)
  • Frequency: Once per day when working

Configuration Analysis

Workflow: .github/workflows/daily-news.md

engine: copilot
timeout-minutes: 30
tracker-id: daily-news-weekday

network:
  allowed:
    - defaults
    - python
    - node

sandbox:
  agent: awf  # Firewall enabled

tools:
  repo-memory:
    branch-name: memory/daily-news
    file-glob: ["memory/daily-news/*.json", "*.jsonl", "*.csv", "*.md"]
    max-file-size: 102400  # 100KB
  edit:
  bash: ["*"]
  web-fetch:

safe-outputs:
  upload-asset:
  create-discussion:
    expires: 3d
    category: "daily-news"
    max: 1
    close-older-discussions: true

Known Issues

Previous Reports

Timeout Pattern Analysis

  • Configuration: 30-minute timeout (reduced from 45 minutes)
  • Note: "Reduced from 45 since pre-fetching data is faster"
  • CI Doctor Fix: Successfully resolved similar timeout issues
  • Opportunity: Apply CI Doctor's fix to Daily News

Investigation Required

Immediate Actions

  1. Review Issue [P1] Daily News Workflow Timeout Failures - 50% Success Rate #9899 - Check current status and investigation progress
  2. Analyze timeout patterns - Determine if exceeding 30-minute limit
  3. Check pre-fetch logic - Verify if data pre-downloading works correctly
  4. Test network access - Validate firewall and network permissions
  5. Compare with CI Doctor - Apply similar timeout resolution approach

Likely Root Causes

  • ✅ Timeout exceeding 30 minutes
  • ✅ Network connectivity issues (firewall restrictions)
  • ✅ Repo-memory access delays
  • ✅ GitHub API rate limiting
  • ✅ Pre-fetch logic not optimized
  • ✅ Tool invocation overhead

Recommended Fix Approach

Short-term (Immediate)

  1. Increase timeout back to 45 minutes temporarily
  2. Monitor run duration to establish baseline
  3. Check pre-fetch effectiveness - Verify it actually speeds up execution
  4. Test without firewall to isolate network issues

Long-term (Optimization)

  1. Apply CI Doctor fix - Use similar timeout resolution strategy
  2. Optimize data collection - Reduce API calls and tool invocations
  3. Improve caching - Better use of repo-memory for historical data
  4. Parallel processing - Fetch data concurrently where possible

Success Criteria

  • Workflow runs successfully with >80% success rate
  • No timeout errors (runs complete within 30 minutes)
  • Daily digest delivered consistently on weekdays
  • Discussion created with repository activity summary
  • Asset uploaded with detailed news data

Related Issue: #9899
Workflow Run: https://github.com/githubnext/gh-aw/actions/runs/21053929777
Generated: 2026-01-16T02:53:12Z
Generated by: Workflow Health Manager

AI generated by Workflow Health Manager - Meta-Orchestrator

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions