A Production Python Telegram Bot Was Crashing Every 2 Hours. The Fix Was 18 Lines.
A production Python Telegram bot was experiencing crashes every 2-3 hours due to a series of cascading errors. The issue was traced back to a lack of throttle middleware, which caused multiple concurrent outbound API calls that exceeded Telegram's rate limits. The solution involved a simple fix of 18 lines of code, after which the bot has remained stable for weeks.
- ▪The bot was crashing due to a combination of TelegramRetryAfter, asyncio.TimeoutError, and sqlite3.OperationalError.
- ▪Initial hypotheses about SQLite being the bottleneck and hitting Telegram API rate limits were proven incorrect.
- ▪The root cause was identified as the absence of throttle middleware, leading to multiple concurrent API calls during peak usage.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/lamas51/a-production-python-telegram-bot-was-crashing-every-2-hours-the-fix-was-18-lines-29di |
| Publication time | Wed, 20 May 2026 13:28:23 +0000 |
| Retrieval time | 2026-05-20T13:35:02.606Z |
| Last seen | 2026-05-20T13:35:02.606Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | iVBzhSwOmtP4 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3942385) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Boris Kl Posted on May 20 A Production Python Telegram Bot Was Crashing Every 2 Hours. The Fix Was 18 Lines. #python #aiogram #asyncio #debugging "If you see cascading errors, find the first thing that fails and stop reading the log there. Everything after the first failure is the system reacting to the first failure." A production Python Telegram bot I was looking after started crashing every 2-3 hours.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
