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.
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)
