#[Bug] Telegram Group-Chat responses failing at internal handoff / 30s secrets.resolve timeout loop

1 messages · Page 1 of 1 (latest)

still trench
#

What I'm trying to do:

• Have Dyson (my OpenClaw agent) respond to messages in a Telegram group chat.
• Private chat (DM) with the same bot works instantly.

What's happening instead:

• Every message to the group takes 5+ minutes to receive a response.
• Log Evidence: Multiple occurrences of gateway secrets.resolve unavailable (gateway timeout after 30000ms) per request.
• Internal Confirmation: Tailing the .jsonl session transcript confirms the agent is generating the response text (e.g., "Yeah, I'm here. What's up?") almost immediately, but the Telegram plugin never delivers it to the group.

Technical Context:

• OpenClaw Version: 2026.4.27
• Environment: Bare-metal systemd service, Ubuntu 24.04, Vultr VPS.
• Verification: I can send messages to the same group ID using curl and the same Bot Token from the same VPS command line, and they arrive instantly. This confirms the Bot Token and network path are valid.
• Group Settings: requireMention: false, allowFrom: ["*"].
• DMs vs Groups: DMs work perfectly; the issue is strictly isolated to group-chat delivery from an embedded agent session.

Findings:

• The group-delivery path in the Telegram provider appears to trigger a WebSocket secrets.resolve call back to the gateway.
• Since the gateway is currently busy managing the active agent session, this call times out (30s), retries, and eventually causes a 5+ minute delay or total delivery failure.

Question:
Is this a known deadlock in the group-delivery logic? Is there a way to pre-resolve these secrets or bypass the WebSocket callback for group-chat handoffs?

silent sleetBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

still trench
#

secrets.resolve gateway timeout loop in Telegram group context — 5min response delays

still trench
#

[Bug] Telegram Group-Chat responses failing at internal handoff / 30s secrets.resolve timeout loop

still trench
#

Update — resolved:

Combination of fixes that got group chat working:
1. Denied exec in the group config — Dyson was using openclaw message send via exec to deliver group replies, which triggered a secrets.resolve WebSocket handshake back to the gateway on every message. Each handshake timed out at 30s. Blocking exec at the group level forced the native Telegram plugin reply path, which works instantly.

"<your-group-id>": {
"requireMention": false,
"allowFrom": ["*"],
"groupPolicy": "allowlist",
"tools": { "deny": ["exec"] }
}

2.    Upgraded to 2026.4.29 — may have also contributed.

Responses are now fast. Thanks for the great product.​​​​​​​​​​​​​​​​