LonamiWebs/Telethon
1
1
Fork 0
mirror of https://github.com/LonamiWebs/Telethon.git synced 2024-11-28 04:13:45 +03:00
Code Issues Packages Projects Releases Wiki Activity

Destroyed RPC errors (markdown)

Lonami 2018-06-25 09:29:26 +02:00
parent 7c57239439
commit 5e3af0baf0
1 changed files with 0 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
RPC-errors.md

@ -1,15 +0,0 @@
RPC stands for Remote Procedure Call, and when Telethon raises an `RPCError`, it's most likely because you have invoked some of the API methods incorrectly (wrong parameters, wrong permissions, or even something went wrong on Telegram's server). The most common are:
* `FloodError` (420), the same request was repeated many times. Must wait `.seconds`. When a `FloodWaitError` occurs, it means that you've executed the same query with the same parameters many times in a short period of time (or even with different parameters in a longer period of time). You need to wait. Telegram is basically telling you to slow down for a bit, not to abuse the API.
* `SessionPasswordNeededError`, if you have setup two-steps verification on Telegram.
* `CdnFileTamperedError`, if the media you were trying to download from a CDN has been altered.
* `ChatAdminRequiredError`, you don't have permissions to perform said operation on a chat or channel. Try avoiding filters, i.e. when searching messages.
The generic classes for different error codes are:
* `InvalidDCError` (303), the request must be repeated on another DC.
* `BadRequestError` (400), the request contained errors.
* `UnauthorizedError` (401), the user is not authorized yet.
* `ForbiddenError` (403), privacy violation error.
* `NotFoundError` (404), make sure you're invoking `Request`'s!
If the error is not recognised, it will only be an ``RPCError``.