Telegram Trigger stopped working unexpectedly

Questions
1

Hi everyone,

I was using the Telegram Trigger node in my workflow and it was working fine before. However, all of a sudden, it stopped triggering from my Telegram messages.

  • My workflow is still active.

  • I haven’t changed anything in the configuration.

  • Other nodes in n8n are working as expected.

  • I don’t see any obvious error message, it just doesn’t trigger anymore when I send a message to the bot.

Has anyone experienced this issue before or know what might cause the Telegram Trigger to suddenly stop working? Any help would be greatly appreciated.

Thanks in advance!

I’m using Docker and ngrok

2

Do the docker logs show any errors when you try to trigger, or any errors related to the workflow stopping/not responding/ etc ?

3

1
11584×730 36.9 KB

2
21579×328 19.3 KB

These are the log. I didn’t see any errors

4

Does the workflow work for a while after restarting n8n? Worfklow could be crashing for some reason. I see a lot of unfinished executions that could signal that.

Also, can you enable debug logs in your compose file and capture logs again if the workflow doesn’t respond:

environment:
      - N8N_LOG_LEVEL=debug
      - N8N_LOG_OUTPUT=console

Or this in the docker run command:

docker run -d \
  --name n8n \
  -p 5678:5678 \
  -e N8N_LOG_LEVEL=debug \
  -e N8N_LOG_OUTPUT=console \
  -v ~/.n8n:/home/node/.n8n \
  n8nio/n8n
5

Try deactivating the workflow and then activating it again.

You might have missed this note:

Due to Telegram API limitations, you can use just one Telegram trigger for each bot at a time

If you already have an active workflow using a Telegram trigger and then create another one (even just for testing), the active workflow will lose its Telegram webhook connection and will stop receiving updates.

1 Like
6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.