SCHEDULE_DATE_INVALID - Gogram TL Reference

Gogram TLRef

HTTP 400 · Bad Request

HTTP 400 Messages

When & why it happens

The supplied schedule date is malformed, points to nothing the server recognises, or fails a server-side validity check.

Handling in gogram

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

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

Related errors

MESSAGE_AUTHOR_REQUIREDMessage author required.MESSAGE_EDIT_TIME_EXPIREDYou can't edit this message anymore, too much time has passed since its creation.MESSAGE_EMPTYThe provided message is empty.MESSAGE_IDS_EMPTYNo message ids were provided.MESSAGE_ID_INVALIDThe provided message id is invalid.MESSAGE_NOT_MODIFIEDThe provided message data is identical to the previous message data, the message wasn't modified.MESSAGE_POLL_CLOSEDPoll closed.MESSAGE_TOO_LONGThe provided message is too long.MSG_ID_INVALIDInvalid message ID provided.MSG_TOO_OLDTime has passed since the message was sent, read receipts were deleted.MSG_WAIT_FAILEDA waiting call returned an error.REACTION_EMPTYEmpty reaction provided.