openclaw - 💡(How to fix) Fix Subagent result exists but requester reports "aborted/no result" due to completion announce timeout (Telegram) [2 comments, 2 participants]

TL;DR

Implement a transport-based completion delivery mechanism to decouple subagent completion announce from model inference and requester agent state.

Guidance

• Investigate using sessions_send or a similar enqueue and retry mechanism to deliver subagent completion results to the requester agent, allowing for retries without requiring the requester to be idle.
• Consider persisting subagent completion results into the requester's history to enable the UI to display "result available" even if the initial announce step fails.
• Review the current implementation of the "direct announce agent call" and identify areas where it can be modified to be more resilient to timeouts and requester agent state.
• Analyze the gateway timeout after 120000ms and stuck session log indicators to understand the frequency and impact of these issues on completion delivery.

Example

No code example is provided as the issue does not contain sufficient implementation details.

Notes

The suggested fix direction implies a need to rearchitect the completion delivery mechanism, which may require significant changes to the existing codebase. Additionally, the v2026.4.25-beta.9 version and Telegram channel may have specific requirements or constraints that need to be considered when implementing the fix.

Recommendation

Apply workaround: Implement a transport-based completion delivery mechanism, as it addresses the suspected root cause of the issue and provides a more resilient solution for delivering subagent completion results to the requester agent.