openclaw - 💡(How to fix) Fix Large attachments silently dropped when agent session is cold/expired [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#60487Fetched 2026-04-08 02:50:30
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Participants

Error Message

When a user sends a message with large attachments (e.g. multiple video files, ~200MB total) to an agent that does not have an active session, the message is silently dropped. The agent never receives the message and no error is surfaced to the sender. 3. Observe: the agent does not respond and no error is shown

  • If the payload is too large to process, an error should be surfaced to the sender (e.g. a reply saying the message could not be processed)
  • No error is shown to the sender

Fix Action

Workaround

Send a short text-only message first to wake the session, then follow up with the large attachments.

RAW_BUFFERClick to expand / collapse

Bug Description

When a user sends a message with large attachments (e.g. multiple video files, ~200MB total) to an agent that does not have an active session, the message is silently dropped. The agent never receives the message and no error is surfaced to the sender.

Steps to Reproduce

  1. Wait for an agent session to go idle/expire (e.g. no activity for 1+ hours, with contextPruning.mode: cache-ttl, ttl: 1h)
  2. Send a message to that agent with large file attachments (tested with 4x MP4 files totaling ~200MB via Discord DM)
  3. Observe: the agent does not respond and no error is shown

Expected Behavior

  • The message should be ingested and a new session spun up, even with large attachments
  • If the payload is too large to process, an error should be surfaced to the sender (e.g. a reply saying the message could not be processed)

Actual Behavior

  • The message is silently dropped
  • No error is shown to the sender
  • The agent appears to be ignoring the user
  • Sending a follow-up text-only message also fails (session is in a bad state)
  • Manually poking the session via sessions_send from another agent works as a workaround

Workaround

Send a short text-only message first to wake the session, then follow up with the large attachments.

Environment

  • OpenClaw version: 2026.3.13
  • Channel: Discord (DM with bot account)
  • OS: macOS (arm64)
  • Gateway mode: local

Additional Context

  • This has been observed multiple times across different agents
  • The issue does not occur when the agent already has an active session
  • Small text-only messages to cold sessions work fine — the issue is specific to large attachment payloads during session creation

extent analysis

TL;DR

Sending a short text-only message to wake the session before sending large attachments is a reliable workaround to prevent messages from being silently dropped.

Guidance

  • Verify that the contextPruning.mode is set to cache-ttl and the ttl is set to 1h to ensure the session is being properly pruned after an hour of inactivity.
  • Test sending large attachments to an agent with an active session to confirm the issue is specific to cold sessions.
  • Use the sessions_send endpoint to manually poke the session and verify it can be successfully woken up.
  • Consider increasing the ttl value or adjusting the contextPruning.mode to see if it affects the behavior of large attachment handling during session creation.

Example

No code snippet is provided as the issue does not require a specific code change, but rather a workaround or configuration adjustment.

Notes

The root cause of the issue is unclear, but it appears to be related to the handling of large attachments during session creation. The provided workaround is reliable, but a more permanent solution may require further investigation into the OpenClaw version or Discord API limitations.

Recommendation

Apply the workaround of sending a short text-only message to wake the session before sending large attachments, as it is a reliable and straightforward solution to prevent messages from being silently dropped.

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