WORKER_BUSY_TOO_LONG_RETRY - Gogram TL Reference

Gogram TLRef

HTTP 400 · Bad Request

HTTP 400 Server / Internal

When & why it happens

The worker busy exceeds the maximum length the server accepts. Shorten it.

Handling in gogram

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

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

Related errors

API_ID_INVALIDAPI ID invalid.API_ID_PUBLISHED_FLOODThis API ID was published somewhere, you can't use it now.CONNECTION_API_ID_INVALIDThe provided API id is invalid.CONNECTION_APP_VERSION_EMPTYApp version is empty.CONNECTION_DEVICE_MODEL_EMPTYDevice model empty.CONNECTION_LANG_PACK_INVALIDThe specified language pack is not valid.CONNECTION_LAYER_INVALIDLayer invalid.CONNECTION_NOT_INITEDConnection not initialized.CONNECTION_SYSTEM_EMPTYConnection system empty.CONNECTION_SYSTEM_LANG_CODE_EMPTYThe system language string was empty during connection.INTERDC_X_CALL_ERRORAn error occurred while communicating with DC %v.INTERDC_X_CALL_RICH_ERRORA rich error occurred while communicating with DC %v.