Telegram notification not working (Discussion #211)

[s-b-e-n-s-o-n]

Source

GitHub Discussion: #211

Report

User @rj10rd reports Telegram notifications are not received when updates are available or containers are updated.

Investigation

QA tested the Telegram trigger end-to-end:

1. Trigger registers correctly from DD_TRIGGER_TELEGRAM_{name}_BOTTOKEN + DD_TRIGGER_TELEGRAM_{name}_CHATID env vars
2. Trigger fires after watcher scan detects updates — sendMessage() calls the Telegram Bot API via axios POST
3. Error handling works — API errors logged as WARN with component name, repeated errors suppressed within 15s window
4. Auto execution enabled by default (auto: all, threshold: all, once: true)

No code bug found. Likely a configuration issue on the user's end (wrong chat ID, bot not in group, invalid token format, etc.).

Status

Awaiting user response with their config and logs.

[s-b-e-n-s-o-n]

Tracking from Discussion #211. QA tested the Telegram trigger end-to-end — no code bug found. Most likely a configuration issue (wrong chat ID, bot not added to group, or invalid token format).

@rj10rd — could you double-check your DD_TRIGGER_TELEGRAM_* env vars against the Telegram trigger docs? Specifically:

• DD_TRIGGER_TELEGRAM_<name>_TOKEN — the bot token from BotFather
• DD_TRIGGER_TELEGRAM_<name>_CHATID — the numeric chat ID (use @userinfobot to find it)

If those look correct, set DD_LOG_LEVEL=debug and share the logs around when a container update is detected — that will show whether the trigger fires and what response Telegram returns.

[s-b-e-n-s-o-n]

Fixed in v1.5.0-rc.2. The root cause was that Telegram MarkdownV2 special characters in container names and version numbers (dots, dashes, parentheses) were not escaped in the message body, causing Telegram API 400 errors. All trigger paths now escape correctly. Please update and let us know if Telegram notifications are working.