docs: add Telegram capacity & limits explanation (#405)#406
Open
Nathan Schram (nathanschram) wants to merge 1 commit into
Open
docs: add Telegram capacity & limits explanation (#405)#406Nathan Schram (nathanschram) wants to merge 1 commit into
Nathan Schram (nathanschram) wants to merge 1 commit into
Conversation
Adds docs/explanation/telegram-capacity.md covering Telegram Bot API limits, Untether's outbox pacing and concurrency model, operating envelope, and scaling patterns. Cross-linked from README Help Guides, troubleshooting, and the transport reference. Also adds a new "Telegram rate limit / flood wait" troubleshooting section and a Quick Start capacity note. Companions issue #405 (per-chat retry_at in TelegramOutbox). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a user-facing capacity-and-limits explanation doc for Untether, prompted by a user question about how many concurrent agents one bot token can realistically handle. Covers Telegram Bot API limits, Untether's outbox pacing and concurrency model, where the system breaks first (RAM → Telegram 30/sec → FDs), and scaling patterns.
Companion issue: #405 (per-chat
retry_atinTelegramOutboxhonouring Bot API 7.8'sparameters.scopefield).Changes
docs/explanation/telegram-capacity.md(~140 lines) — authoritative single-source explanation, Diátaxis "explanation" categoryTest plan
python3 scripts/validate_release.pypasses (docs-only, no version bump required)telegram-capacitycross-references resolve (grep + relative path check)#telegram-rate-limit--flood-waitmatches GitHub's slug for the new troubleshooting heading🤖 Generated with Claude Code