openclaw - 💡(How to fix) Fix Bug: sessions_spawn Completion Event Push Failure on Feishu Channel [1 comments, 2 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#72638Fetched 2026-04-28 06:33:48
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Timeline (top)
closed ×1commented ×1cross-referenced ×1

Root Cause

Root Cause (suspected)

Completion event push mechanism is broken on Feishu channel. Event is not routed back to parent session.

Fix Action

Workaround

  • Use result.json file to return results instead of relying on event push
  • Use serial execution instead of sessions_spawn
RAW_BUFFERClick to expand / collapse

Environment

  • OpenClaw: 2026.4.22+
  • Channel: Feishu
  • Model: minimax/MiniMax-M2.7

Issue

sessions_spawn successfully dispatches subagent, subagent completes normally, but completion event does NOT push back to parent session on Feishu channel.

Reproduction Steps

  1. main session (Feishu) calls sessions_spawn with agentId="coder"
  2. subagent executes normally (fibonacci test completed with result fib(10)=55)
  3. subagent completes with result
  4. Expected: completion event pushes back to parent session
  5. Actual: parent session waits 30s, then shows "Something went wrong"

Root Cause (suspected)

Completion event push mechanism is broken on Feishu channel. Event is not routed back to parent session.

Workaround

  • Use result.json file to return results instead of relying on event push
  • Use serial execution instead of sessions_spawn

Impact

  • sub-agent scheduling: works ✅
  • result return: broken ❌
  • main session: hangs and errors ❌

extent analysis

TL;DR

Implement a workaround by using the result.json file to return results instead of relying on the event push mechanism.

Guidance

  • Verify that the subagent is correctly writing its result to the result.json file.
  • Modify the main session to poll for the result.json file instead of waiting for the completion event.
  • Consider using serial execution instead of sessions_spawn as an alternative workaround.
  • Test the workaround with a simple scenario to ensure it works as expected before applying it to more complex cases.

Example

No code snippet is provided as the issue does not contain sufficient information about the code implementation.

Notes

The provided workaround assumes that the result.json file is correctly written by the subagent and that the main session can access this file. Additional error handling may be necessary to ensure robustness.

Recommendation

Apply the workaround using the result.json file, as it provides a clear and feasible solution to the problem, allowing the main session to retrieve the result from the subagent without relying on the broken event push mechanism.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Bug: sessions_spawn Completion Event Push Failure on Feishu Channel [1 comments, 2 participants]