Telegram notification not working

[rj10rd]

When update available or container updated there is no notification recieved on telegram

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

Hey @rj10rd 👋 — a few things to check:

1. Verify your env vars are set correctly

You need at minimum:

DD_TRIGGER_TELEGRAM_{name}_BOTTOKEN=your-bot-token
DD_TRIGGER_TELEGRAM_{name}_CHATID=your-chat-id

Replace {name} with any label you want (e.g. 1, MYBOT, etc.).

2. Check the logs

Look for these in your Drydock logs:

• Register all components of kind trigger for provider telegram — confirms the trigger loaded
• Registering for auto execution with component: trigger.telegram.* — confirms it will fire automatically
• Any WARN or ERROR lines mentioning trigger.telegram — these would show API errors from Telegram

3. Common issues

• Wrong chat ID — make sure you're using the numeric chat ID, not the username. For groups, the ID is negative (e.g. -1001234567890). You can get it from the Telegram Bot API getUpdates endpoint after sending a message to your bot.
• Bot not added to group — if using a group chat, the bot must be a member of that group.
• Bot token format — should look like 123456789:AABBccDDeeFF... (number, colon, alphanumeric string).
• once: true (default) — triggers only fire once per container update. If you've already seen the update in the UI but the trigger errored on the first attempt, it won't retry. Restart Drydock to reset.

Could you share:

1. Your Telegram-related environment variables (redact the bot token)
2. The relevant log output from startup and after a scan completes

Docs for reference: https://getdrydock.com/docs/configuration/triggers/telegram

[rj10rd]

Sir i want to talk you personally 😊

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

No need my friend! Thank you for hanging out!

[rj10rd]

Thanks sir but my wedding on 21 april so I am busy and I want only to invite you on wedding. thank for this awesome app i give feedback after my wedding but telegram notification not working.

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

@rj10rd Congratulations on your wedding! 🎉 We would love to come!

Good news — we found and fixed the Telegram notification bug. The issue was that MarkdownV2 special characters in container names and version numbers (dots, dashes, parentheses, etc.) were not being escaped in the message body, which caused the Telegram API to reject the message with a 400 error. So your trigger was configured correctly — it was a bug on our side.

The fix is shipping in RC2 which is going out today. Once you're back from celebrating, update to the latest version and your Telegram notifications should just work.

Enjoy the wedding! We'll be here when you're ready. 🥂

[rj10rd]