Enum TelegramError 

pub enum TelegramError {
    InvalidToken(String),
    MessageTooLarge {
        bytes: usize,
        max: usize,
    },
    Http(Error),
    Api {
        error_code: i32,
        description: String,
    },
    RateLimited {
        retry_after: Duration,
    },
    Serialization(Error),
    Internal(String),
}

Every way a Telegram send can fail.

Note that TelegramError::Http always holds a reqwest::Error which has had its URL stripped via reqwest::Error::without_url. The bot token is a path segment of every request URL, and reqwest’s own Debug includes the URL, so an un-stripped error would leak the credential into any log line.

Variants

InvalidToken(String)

The bot token was empty or malformed.

MessageTooLarge

The message was too large to even attempt to send.

This is a guard against an upstream bug producing a multi-megabyte string; it is checked before chunking, so it is never the result of merely exceeding Telegram’s per-message limit.

Fields

bytes: usize

Size of the offending message, in bytes.

max: usize

The maximum permitted size, in bytes.

Http(Error)

The HTTP request itself failed (connection refused, TLS failure, timeout).

Api

Telegram accepted the request but rejected its contents.

Fields

error_code: i32

Telegram’s error_code (an HTTP status code).

description: String

Telegram’s human-readable description.

RateLimited

Telegram returned 429 along with how long to wait.

This is distinct from a plain TelegramError::Api 429 because it carries an actionable delay: Telegram is telling us precisely when the request may be repeated.

Fields

retry_after: Duration

How long Telegram asked us to wait.

Serialization(Error)

The response body could not be deserialized.

Internal(String)

An invariant inside this library was violated.

Implementations

impl TelegramError

pub const fn is_permanent(&self) -> bool

Whether this error is permanent, meaning a retry can never succeed.

A permanent error almost always means the notifier is misconfigured rather than that this particular message was bad: a wrong token, a chat the bot was removed from, a chat id that does not exist. Every subsequent send will fail the same way.

pub fn is_misconfiguration(&self) -> bool

Whether this error indicates the notifier as a whole is misconfigured.

These deserve a louder log than an ordinary send failure, because they mean every future send is also doomed:

• 401 — the bot token is wrong.
• 403 — the bot was blocked, or removed from the chat.
• 400 with a chat-related description — the chat id is wrong.

Trait Implementations

impl Debug for TelegramError

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Display for TelegramError

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Error for TelegramError

fn source(&self) -> Option<&(dyn Error + 'static)>

Returns the lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0:

use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0:

replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type-based access to context intended for error reports.

impl From<Error> for TelegramError

fn from(error: Error) -> Self

Converts to this type from the input type.

impl From<Error> for TelegramError

fn from(error: Error) -> Self

Converts to this type from the input type.