Telegram Trigger don't work

Hi all!
I created the docker link according to the article Docker Compose - n8n Documentation and everything seems to work (e.g. webhook) but I am interested in the Telegram Trigger, I put the necessary BOT API, and click Execute workflow, after that whatever I did with the bot, the trigger does not work and workflow cannot be stopped, trying to do this brings up an error :

Problem stopping execution
The execution ID “7” could not be found.

I don’t know what this means and what to do about it. The following is written in the logs:

8n ready on 0.0.0.0, port 5678
Version: 0.186.1

Editor is now accessible via:
https://mysubdomain.mydomain.com:5678/
/usr/local/lib/node_modules/n8n/dist/src/TestWebhooks.js:62
            clearTimeout(this.testWebhookData[webhookKey].timeout);
                                                          ^

TypeError: Cannot read properties of undefined (reading 'timeout')
    at /usr/local/lib/node_modules/n8n/dist/src/TestWebhooks.js:62:59
Initializing n8n process
n8n ready on 0.0.0.0, port 5678
Version: 0.186.1

Editor is now accessible via:
https://mysubdomain.mydomain.com:5678/

What can it be and what can I do, please help me to solve this problem, maybe I am doing something wrong?
The certificates are valid and the browser does not complain about their absence or insecure connection:

Please share the workflow

Share the output returned by the last node

Execution ID: 4 of “My workflow” workflow

Information on your n8n setup

  • n8n version: 0.186.1
  • **Running n8n with the execution process [own(default), main]: **
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: docker compose

Here’s some more data, on the telegram trigger here’s the request:
Screenshot_26

There is an error when you try to go:
404 page not found

And there is also sometimes an error:
Bad gateway

If you try to save the workflow and then run it through the “execute” button, you get an error:

Problem running workflow
Cannot read properties of undefined (reading 'statusCode')

Okay, I don’t know what happened, but the virtual machine froze and I had to forcibly reboot it. After that everything started working as it should, telegram trigger responds to everything I need.

1 Like