Trigger Telegram parou depois da atualização 2.3.6

Questions
1

If your question hasn’t been asked before, please follow the template below. Skip the questions that are not relevant to you. →

Describe the problem/error/question

Depois que atualizei o Trigger Telegram nunca é acionado

What is the error message (if any)?

Não aparece erro pois nem acionar o trigger

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 3.6.2
  • Database (default: SQLite): SQLITE
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): NPM
  • Operating system: WINDOWS 10 SERVER 2016
2

After the update to 2.3.6, it’s possible there were changes in how the Telegram Trigger node handles updates. First, double-check your Telegram Bot token and that the bot is still active. Then, review the Telegram Trigger node’s settings to ensure they’re configured correctly, including the “Update Types” you’re listening for. If the issue persists, you might want to consult the n8n documentation on Telegram Trigger node common issues for troubleshooting tips.

3

Atualizei o N8N novamente, tirei e coloquei credencial do Telegram, recriei todo o workflow, e mesmo assim não está captando nada, inclusive quando excluo e coloco a credencial novamente ele faz conexão normalmente ;(

4

I would check your instance logs to see if there is anymore information.

1 Like
5

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