Bug: Empty task output breaks fallback system #29054

Activity

1. github-actions

   assigned

   kitlangton

   on May 24, 2026
2. github-actions commented on May 24, 2026

   

   github-actionsBot

   on May 24, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of an existing issue. Please check:

   • TaskTool returns no diagnostic context when subagent result text is empty or missing #24447: Covers the same root cause — TaskTool silently returns an empty string when the subagent result has no text part (the ?? "" fallback), and discusses the same problem of empty <task_result> breaking downstream behavior.
3. niStee commented on May 27, 2026

   

   niStee

   on May 27, 2026

   Author

   More actions

   Note: I've opened a related issue (#29470) tracking a sibling edge case: when the LLM provider API connection hangs indefinitely without returning any data or throwing an HTTP error, it entirely bypasses the fallback chain since the stream never completes.
4. niStee commented on May 27, 2026

   

   niStee

   on May 27, 2026

   Author

   More actions

   Closing as a duplicate of the earlier issue #24447! PR #29048 implements the fix for this.
5. niStee

   closed this as not plannedon May 27, 2026