Increase chroma-issue-indexer timeout to 30 minutes

[Copilot]

Workflow run #21779860896 timed out at 21.7 minutes, exceeding the default 20-minute limit for agentic workflows.

Changes

• Added timeout-minutes: 30 to workflow frontmatter
• Recompiled workflow to apply timeout to execution step

The 30-minute limit provides adequate headroom (38% margin) for the observed runtime while remaining conservative.

engine:
  id: copilot
  model: gpt-5.1-codex-mini
timeout-minutes: 30  # Added
imports:
  - shared/mood.md
  - shared/mcp/chroma.md

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[plan] Fix Chroma Issue Indexer Timeout Issue</issue_title>
<issue_description>## Objective

Investigate and fix the Chroma Issue Indexer failure that occurred after a 21.7 minute runtime, either by increasing timeout or optimizing performance.

Context

From Discussion github/gh-aw#14345, the Chroma Issue Indexer §21779860896 failed after running for 21.7 minutes.

This could indicate:

• Timeout configured too low for typical workload
• Performance degradation due to data growth
• Inefficient processing logic

Approach

1. Download and analyze logs from the failed run using gh aw logs
2. Determine if failure was due to timeout or other error
3. Review Chroma Issue Indexer workflow configuration:
   • Current timeout settings
   • Processing logic and efficiency
   • Data volume being processed
4. Identify root cause:
   • Is timeout too aggressive for normal operation?
   • Are there performance bottlenecks in indexing logic?
   • Is data volume growing beyond expectations?
5. Implement appropriate fix:
   • If timeout issue: increase timeout-minutes in workflow
   • If performance issue: optimize indexing logic (batch processing, parallel operations)
   • If data volume issue: implement incremental indexing

Files to Modify

• .github/workflows/chroma-issue-indexer.md - Workflow definition
• Related indexing logic files if performance optimizations needed

Acceptance Criteria

• Root cause identified and documented
• Appropriate fix implemented (timeout increase or performance optimization)
• Test run completes successfully without timeout
• If performance optimized, document improvements achieved
• Consider monitoring for future timeout issues

AI generated by Plan Command for discussion #14345

• expires on Feb 9, 2026, 2:05 PM UTC

Comments on the Issue (you are @copilot in this section)

• Fixes [plan] Fix Chroma Issue Indexer Timeout Issue #14354

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.