# \[solved\] Intermittent behavior of Telegram bot

**URL:** <https://discourse.nodered.org/t/solved-intermittent-behavior-of-telegram-bot/13367>\
**Category:** General\
**Created:** [16 July 2019 15:47 UTC](https://discourse.nodered.org/t/solved-intermittent-behavior-of-telegram-bot/13367 "2019-07-16T15:47:01Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![GerardWassink](https://avatars.discourse-cdn.com/v4/letter/g/a3d4f5/32.png) [@GerardWassink](https://discourse.nodered.org/u/GerardWassink)\
**Post date:** [16 July 2019 15:47 UTC](https://discourse.nodered.org/t/solved-intermittent-behavior-of-telegram-bot/13367/1 "2019-07-16T15:47:01Z")

</div>

Good afternoon guys,

I'm using node-red-contrib-telegrambot version 4.4.2 and overall it performs well, albeit that It does not reacts reliably. I use it to ask for status information.

It has a few 'commands':

- /Start
- /home
- /help

Now sometimes it reacts immediately, other times it does not react at all, most of the time intermittently. Anyone has had similar experience (and hopefully a solution)?

Gerard

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [16 July 2019 15:51 UTC](https://discourse.nodered.org/t/solved-intermittent-behavior-of-telegram-bot/13367/2 "2019-07-16T15:51:41Z")

</div>

If you look at the issue list for teh node on github you will find [https://github.com/windkh/node-red-contrib-telegrambot/issues/74](https://github.com/windkh/node-red-contrib-telegrambot/issues/74) which was closed because they couldn't reproduce it.

Perhaps you could add your details to the issue and work with the developer to problem solve it.

---

<div class="post-metadata">

**Author:** ![GerardWassink](https://avatars.discourse-cdn.com/v4/letter/g/a3d4f5/32.png) [@GerardWassink](https://discourse.nodered.org/u/GerardWassink)\
**Post date:** [16 July 2019 16:17 UTC](https://discourse.nodered.org/t/solved-intermittent-behavior-of-telegram-bot/13367/3 "2019-07-16T16:17:04Z")

</div>

Thanks for the pointer moose, I reported it there as well.

---

<div class="post-metadata">

**Author:** ![GerardWassink](https://avatars.discourse-cdn.com/v4/letter/g/a3d4f5/32.png) [@GerardWassink](https://discourse.nodered.org/u/GerardWassink)\
**Post date:** [16 July 2019 17:37 UTC](https://discourse.nodered.org/t/solved-intermittent-behavior-of-telegram-bot/13367/4 "2019-07-16T17:37:54Z")

</div>

I think I may have found it. When I open one of my four command nodes, i can choose the bot name. When I open the drop-down list I see three bots with the same name; presumably because early in the process I've been heavily testing... The two commands that where working made use of the second of the three choices (again: with the same name). The other ones used the third entry. I changed the last two now so they make use of the second bot-choice.

Up until now they have not missed a beat!

Gerard

---

<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:** [16 July 2019 20:05 UTC](https://discourse.nodered.org/t/solved-intermittent-behavior-of-telegram-bot/13367/5 "2019-07-16T20:05:07Z")

</div>

Yes, you can only have one app controlling one bot id otherwise it doesn't work.

I've added a suggestion on how to provide an ID check to the admin UI in the issue.

---

<div class="post-metadata">

**Author:** ![GerardWassink](https://avatars.discourse-cdn.com/v4/letter/g/a3d4f5/32.png) [@GerardWassink](https://discourse.nodered.org/u/GerardWassink)\
**Post date:** [17 July 2019 04:50 UTC](https://discourse.nodered.org/t/solved-intermittent-behavior-of-telegram-bot/13367/6 "2019-07-17T04:50:33Z")

</div>

I saw that TI, I will close this topic and wait for Julian to solve it in his software. My direct problem has been solved.  
Thanks for participating all,  
Gerard

---

<div class="post-metadata">

**Author:** ![GerardWassink](https://avatars.discourse-cdn.com/v4/letter/g/a3d4f5/32.png) [@GerardWassink](https://discourse.nodered.org/u/GerardWassink)\
**Post date:** [17 July 2019 04:59 UTC](https://discourse.nodered.org/t/solved-intermittent-behavior-of-telegram-bot/13367/7 "2019-07-17T04:59:19Z")

</div>

Having said that, I cannot for the life of me find a way to close a topic, is that even possible on this forum, or do we just 'leave them hanging'?

---

<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:** [17 July 2019 06:00 UTC](https://discourse.nodered.org/t/solved-intermittent-behavior-of-telegram-bot/13367/8 "2019-07-17T06:00:27Z")

</div>

You can just add "[Solved] " to the start of the title so that people know that there is an answer.

---

<div class="post-metadata">

**Author:** ![GerardWassink](https://avatars.discourse-cdn.com/v4/letter/g/a3d4f5/32.png) [@GerardWassink](https://discourse.nodered.org/u/GerardWassink)\
**Post date:** [17 July 2019 06:35 UTC](https://discourse.nodered.org/t/solved-intermittent-behavior-of-telegram-bot/13367/9 "2019-07-17T06:35:45Z")

</div>

If that's the common practice here, I will adhere of course.  
Thanks.