USER_ALREADY_PARTICIPANT - Gogram TL Reference

Gogram TLRef

HTTP 400 · Bad Request

HTTP 400 Users & Peers

When & why it happens

The user is already participant; the operation would be a no-op.

Handling in gogram

Surfaced as *gogram.ErrResponseCode. Match on the message:

if err, ok := err.(*gogram.ErrResponseCode); ok {
    if err.Message == "USER_ALREADY_PARTICIPANT" {
        // handle this error
    }
}

Related errors

CONTACT_ADD_MISSINGContact to add is missing.CONTACT_ID_INVALIDThe provided contact ID is invalid.CONTACT_MISSINGThe specified user is not a contact.CONTACT_NAME_EMPTYContact name empty.CONTACT_REQ_MISSINGMissing contact request.INPUT_USER_DEACTIVATEDThe specified user was deleted.PEER_FLOODToo many requests.PEER_HISTORY_EMPTYYou can't pin an empty chat with a user.PEER_ID_INVALIDThe provided peer id is invalid.PEER_ID_NOT_SUPPORTEDThe provided peer ID is not supported.USERNAME_INVALIDThe provided username is not valid.USERNAME_NOT_MODIFIEDThe username was not modified.