[Bug Bash 4/17] Agent claims Telegram message sent but no message is delivered

[joe-rlo]

Environment

hosted-staging (crab shack)

Version / Commit Hash

staging-2026-04-17

QA Test Date

2026-04-17

Feature Area

Telegram channel → message delivery

Steps to Reproduce

1. Connect Telegram bot to agent via Settings → Telegram
2. Send a message in the web UI requesting the agent to send a Telegram message (e.g. "Send me a hello message on Telegram")
3. Observe the agent's response in the web UI
4. Check the Telegram app for the message

Expected Behavior

The agent should successfully deliver the message to the connected Telegram chat. The message should appear in the Telegram app.

Actual Behavior

The agent responds in the web UI stating "Message has been sent to your Telegram" (or similar confirmation), but no message actually arrives in the Telegram app. The agent falsely reports success despite the message never being delivered. Observed across multiple use cases during the 4/17 bug bash session. Related to #2279 (closed) which tracked a similar false-success pattern with shell/open tool errors.

Logs / Screenshots

Discovered during Bug Bash 4/17 session (UC1: Send message via Telegram). Agent confirms delivery but Telegram app shows no incoming message.

Pre-submit checklist

• Title is specific (not "fix Google Suite" but "Google Suite install throws invalid_grant on OAuth step")
• Commit hash is filled in
• Steps are numbered and reproducible

[joe-rlo]

Bug Bash 4/20 update: Telegram notifications from missions are still not being delivered on staging (v0.25.0). Missions that include a "send via Telegram" step report success in the UI, but no message arrives in the Telegram app. This is now compounded by the mission_create null cooldown_secs issue (#2741) which blocks new mission creation entirely. The linked PR #2714 (review-driven guidance for Claude Code) may address the false-success pattern but the underlying delivery failure needs separate attention.