Telegram Trigger stops receiving messages after 12–24 hours (n8n Cloud)

Questions
,
1

Hi everyone!

We’re currently facing an issue with the Telegram Trigger node in our n8n Cloud workspace.

Everything works fine when the workflow is first activated, but after 12–24 hours, the trigger stops receiving messages, even though the workflow remains active. We’ve already implemented a workaround using a Cron node and HTTP Request to re-register the webhook every day, but the issue still happens.

Details:

  • Using n8n Cloud (hosted version)
  • Only one workflow uses the bot
  • Only one Telegram bot is active
  • We’re not duplicating triggers
  • Webhook info looks normal when checked via Telegram API

Has anyone else experienced this issue or found a stable solution?
We’d appreciate any insights!

Thanks in advance :pray:

2

Try use “Polling” mode instead of Webhook. If you can switch to a polling approach, try using the Telegram > Get Updates method (manually via HTTP Request node or custom polling) instead of relying on the webhook. Polling doesn’t rely on webhooks staying alive and is often more reliable for long-running bots on hosted environments like n8n Cloud.

Also, sometimes, n8n-hosted workflows get paused due to inactivity or platform constraints. Set up a second Cron workflow that hits the Telegram Trigger workflow via an HTTP request (using n8n’s webhook URL) every few hours. This keeps it “awake” and helps prevent disconnects.

Hope this helps