openclaw - 💡(How to fix) Fix Subagent announce silently drops results after retry exhaustion [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#62054Fetched 2026-04-08 03:09:39
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Participants

Code Example

Subagent announce give up (retry-limit) run=8fb32aa4 child=agent:gepeto:subagent:a6fc8977 requester=agent:gepeto:main retries=3 endedAgo=183s

---

Subagent announce completion direct announce agent call transient failure, retrying 3/4 in 10s: gateway timeout after 120000ms
RAW_BUFFERClick to expand / collapse

Bug

When a subagent completes but the parent session is busy (mid-turn handling user messages), the announce event times out after 120s. It retries 3-4 times, then silently gives up and the result is never delivered to the parent.

Evidence from gateway.log

Subagent announce give up (retry-limit) run=8fb32aa4 child=agent:gepeto:subagent:a6fc8977 requester=agent:gepeto:main retries=3 endedAgo=183s

Multiple instances of:

Subagent announce completion direct announce agent call transient failure, retrying 3/4 in 10s: gateway timeout after 120000ms

Impact

Parent agent promises user 'I'll be back with results' but never delivers. User has to ask 'what happened?' to trigger manual check. Bad UX.

Expected behavior

Announce events should be queued durably and delivered when the parent session becomes available, not fire-and-forget with a limited retry window.

Suggested fix

  • Persistent announce queue (e.g. write to tasks/events)
  • Or: increase retry window significantly (e.g. 10min with backoff)
  • Or: let parent poll for missed announces at turn-start

Environment

  • OpenClaw 2026.4.5
  • 3 agents on single gateway
  • Happens most when user is actively chatting while subagents complete in background

extent analysis

TL;DR

Implement a persistent announce queue to ensure durable delivery of announce events to the parent session.

Guidance

  • Consider increasing the retry window significantly (e.g., 10 minutes with backoff) as a temporary workaround to reduce the likelihood of silent give-ups.
  • Evaluate the feasibility of letting the parent poll for missed announces at turn-start as an alternative solution.
  • Assess the current system's capacity to handle concurrent user chats and subagent completions to identify potential bottlenecks.
  • Review the gateway's configuration and logs to understand the root cause of the gateway timeout after 120000ms.

Example

No code snippet is provided due to the lack of specific implementation details in the issue.

Notes

The suggested fix implies that the current implementation is fire-and-forget, which may not be suitable for the required use case. The persistent announce queue solution may require significant changes to the existing architecture.

Recommendation

Apply a workaround, such as increasing the retry window or implementing parent polling, as a temporary solution until a more robust persistent announce queue can be implemented. This is because the silent give-up issue has a significant impact on user experience, and a workaround can help mitigate this issue in the short term.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Announce events should be queued durably and delivered when the parent session becomes available, not fire-and-forget with a limited retry window.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING