Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #5447] [BUG]: Hitting Telegram limits #5093

New Issue
Closed
opened 2026-06-05 14:51:58 -04:00 by yindo · 1 comment
yindo commented 2026-06-05 14:51:58 -04:00
Owner
Copy Link
Copy Source

Originally created by @deenle on GitHub (Apr 15, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5447

How are you running AnythingLLM?

All versions

What happened?

Hi!
@shatfield4 thanks for implementing Telegram bot support!

Unfortunately, I'm hitting Telegram limits while using it.

[backend] info: [89:807]: Edit error: ETELEGRAM: 429 Too Many Requests: retry after 137
[bg-worker][handle-telegram-chat-1776263235281] info: [89:807]: Edit error: ETELEGRAM: 429 Too Many Requests: retry after 137

Their website says:
https://core.telegram.org/bots/faq#my-bot-is-hitting-limits-how-do-i-avoid-this

  • In a single chat, avoid sending more than one message per second. We may allow short bursts that go over this limit, but eventually you'll begin receiving 429 errors.

Seems like it would be better if we increase STREAM_EDIT_INTERVAL to 1000-1500 ms.
Though, I'd rather send initial message e.g. Thinking and then provide a composed message due to inability to render Markdown while streaming.

https://github.com/Mintplex-Labs/anything-llm/blob/43e79d3b267ed551443dd5c09d0c42124c888eb6/server/utils/telegramBot/constants.js#L4

Are there known steps to reproduce?

No response

LLM Provider & Model (if applicable)

No response

Embedder Provider & Model (if applicable)

No response

Originally created by @deenle on GitHub (Apr 15, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5447 ### How are you running AnythingLLM? All versions ### What happened? Hi! @shatfield4 thanks for implementing Telegram bot support! Unfortunately, I'm hitting Telegram limits while using it. ``` [backend] info: [89:807]: Edit error: ETELEGRAM: 429 Too Many Requests: retry after 137 [bg-worker][handle-telegram-chat-1776263235281] info: [89:807]: Edit error: ETELEGRAM: 429 Too Many Requests: retry after 137 ``` Their website says: https://core.telegram.org/bots/faq#my-bot-is-hitting-limits-how-do-i-avoid-this - In a single chat, avoid sending more than **one message per second**. We may allow short bursts that go over this limit, but eventually you'll begin receiving 429 errors. Seems like it would be better if we increase `STREAM_EDIT_INTERVAL` to 1000-1500 ms. Though, I'd rather send initial message e.g. `Thinking` and then provide a composed message due to inability to render Markdown while streaming. https://github.com/Mintplex-Labs/anything-llm/blob/43e79d3b267ed551443dd5c09d0c42124c888eb6/server/utils/telegramBot/constants.js#L4 ### Are there known steps to reproduce? _No response_ ### LLM Provider & Model (if applicable) _No response_ ### Embedder Provider & Model (if applicable) _No response_
yindo added the possible bug label 2026-06-05 14:51:58 -04:00
yindo closed this issue 2026-06-05 14:51:58 -04:00
yindo commented 2026-06-05 14:51:59 -04:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Apr 15, 2026):

Moved it to a higher interval since edits apparently count as sends as well

<!-- gh-comment-id:4254058960 --> @timothycarambat commented on GitHub (Apr 15, 2026): Moved it to a higher interval since edits apparently count as sends as well
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#5093
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?