# Telegram node problem. Have to spam command to work

**URL:** <https://discourse.nodered.org/t/telegram-node-problem-have-to-spam-command-to-work/60077>\
**Category:** General\
**Created:** [19 March 2022 12:48 UTC](https://discourse.nodered.org/t/telegram-node-problem-have-to-spam-command-to-work/60077 "2022-03-19T12:48:47Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ilse.markert](https://avatars.discourse-cdn.com/v4/letter/i/ebca7d/32.png) [@ilse.markert](https://discourse.nodered.org/u/ilse.markert)\
**Post date:** [19 March 2022 12:48 UTC](https://discourse.nodered.org/t/telegram-node-problem-have-to-spam-command-to-work/60077/1 "2022-03-19T12:48:47Z")

</div>

![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/1/a1c68aaa2dfff776023fb19b59bc735c326d32fb.png)

Hi, I just made a telegram bot for simple interatctions. It kind of works _but_  
for the commands to be recognized and trigger a response I have to literally spam the commands like 5-20 times in the telegram channel until I get a response.

The flow says "polling" most of the time. Sometimes "polling error" and sometimes "connected". During connected the command seems to trigger the response.  
Polling rate is 300

hope someone has an idea

---

<div class="post-metadata">

**Author:** ![achrafb](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/achrafb/32/45607_2.png) [@achrafb](https://discourse.nodered.org/u/achrafb)\
**Post date:** [19 March 2022 14:45 UTC](https://discourse.nodered.org/t/telegram-node-problem-have-to-spam-command-to-work/60077/2 "2022-03-19T14:45:08Z")

</div>

You may be using the same bot token on another machine? or instance

---

<div class="post-metadata">

**Author:** ![ilse.markert](https://avatars.discourse-cdn.com/v4/letter/i/ebca7d/32.png) [@ilse.markert](https://discourse.nodered.org/u/ilse.markert)\
**Post date:** [19 March 2022 14:48 UTC](https://discourse.nodered.org/t/telegram-node-problem-have-to-spam-command-to-work/60077/3 "2022-03-19T14:48:35Z")

</div>

no, only using the bot in this flow

---

<div class="post-metadata">

**Author:** ![ilse.markert](https://avatars.discourse-cdn.com/v4/letter/i/ebca7d/32.png) [@ilse.markert](https://discourse.nodered.org/u/ilse.markert)\
**Post date:** [19 March 2022 15:14 UTC](https://discourse.nodered.org/t/telegram-node-problem-have-to-spam-command-to-work/60077/4 "2022-03-19T15:14:50Z")

</div>

okay yeah....lmfao. There was a second bot with the same name and token...  
am dumb.. ignore xD

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [19 March 2022 16:25 UTC](https://discourse.nodered.org/t/telegram-node-problem-have-to-spam-command-to-work/60077/5 "2022-03-19T16:25:54Z")

</div>

> [@ilse.markert](#):
>
> The flow says "polling" most of the time

That is normal.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/b/7be61fb3d988a4e0cd611bc90c18b52f9c3b6214.png)

I only have one output node that says connected. The rest all say polling.

But the connection is very reliable.

Have you turned on the additional logging to the Node-RED Log?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [18 May 2022 16:26 UTC](https://discourse.nodered.org/t/telegram-node-problem-have-to-spam-command-to-work/60077/6 "2022-05-18T16:26:09Z")

</div>

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