Message Errors

11 April 2024

This article describes the errors that may occur in the following cases:

  • sending messages;
  • checking cascades;
  • receiving message statuses.
The list of errors can be extended. Keep this in mind when setting up the integration.

Message Sending Errors

Errors after calling the schedule method. For more information about the method, see the article.

Error codeErrorDescription
400RequestId is not unique.This request ID has already been used. Use a new ID for each request.
400Content not specified.The content type and its properties are not specified. For example, smsContent, viberContent или whatsappContent.
400ContentType not specified.The content type is not specified. For example, text или image.
400Text not specified.The text field is not filled in.
400Caption not specified.The signature text field is not filled in.
400Action not specified.The action for the button is not specified.
400AttachmentName not specified.The attached document name is not specified.
400AttachmentName is too long.The attached document name is too long. The maximum length is 70 characters.
400Latitude not specified.Latitude is not set when specifying coordinates.
400Longitude not specified.Longitude is not set when specifying coordinates.
400Cascade not found.Invalid cascade ID specified. Request a list of all cascades on your account and verify that the ID you entered is correct.
400Request doesn’t contain content for all cascade stages.The cascade has many channels. Add another channel to the request’s content object.
400Matched template not found.The request body scheme doesn’t match the template scheme. Check the relative location and availability of all properties in the request.
400Cascade scheduling request is not valid.The transmitted content for the cascade doesn’t match the cascade settings. For examples with explanations, see the section.
401Auth error.Authorization error. Check the spelling and expiration date of the API key.
404Not found.The URL you requested was not found. Make sure the address you entered is correct.
405Method not allowed.The HTTP request method is not allowed. Use POST, GET, and other requests according to the documentation.
500System error.Server error. Send a request to the technical support support@edna.io. An error may occur if the request is incorrect. Check the relative location, availability, and completeness of all request properties according to the documentation.

Cascade Checking Errors

Error codeErrorDescription
400Сascade scheduling request not valid.The edna Pulse software performs an additional cascade check when it receives a request to send a message using the cascade/schedule method.
If the received request doesn’t match the cascade parameters, an error is returned with explanations in the detail field. Read the explanations to identify and resolve the discrepancy, or send a request to technical support support@edna.io.
Response format 
{
    "title": "cascade-scheduling-request-not-valid",
    "status": 400,
    "detail": "<details>"
}

Examples of Cascade Checking Errors

Example 1. The content object has channel parameters that are not included in the cascade.

In the request below, the smscontent parameter causes an error, because the cascade with cascadeId = 31634 includes only Viber and WhatsApp channels.

curl --location 'http://app.edna.io/api/cascade/schedule' \
--header 'Content-Type: application/json' \
--header 'x-api-key: ************' \
--data '{
    "requestId": "e62b4736-1278-4119-8816-3f2257eec47c",
    "cascadeId": 31634,
    "subscriberFilter": {
        "address": "+00000000000",
        "type": "PHONE"
    },
    "content": {
        "viberContent": {
            "contentType": "TEXT",
            "text": "cascade viber  --> whatsapp "
        },
        "whatsappContent": {
            "contentType": "TEXT",
            "text": "cascade viber  --> whatsapp"
        },
        "smsContent": {
            "contentType": "TEXT",
            "text": "cascade viber  --> whatsapp"
        }
    }
}'

Response:

{
    "title": "cascade-scheduling-request-not-valid",
    "status": 400,
    "detail": "Cascade scheduling request is not valid. Violations: the cascade template stage was not found for the content [cascadeTemplateId:31,634;contentChannelType:SMS]"
}
Example 2. The content object has no channel parameters that are included in the cascade.

In the request below, only the viberContent parameter is passed, even though the cascade with cascadeId = 31634 includes Viber and WhatsApp channels.

curl --location 'http://app.edna.io/api/cascade/schedule' \
--header 'Content-Type: application/json' \
--header 'x-api-key: ****************' \
--data '{
    "requestId": "7c42344c-aeea-41c9-834b-eb627136f400",
    "cascadeId": 31634,
    "subscriberFilter": {
        "address": "+00000000999",
        "type": "PHONE"
    },
    "content": {
        "viberContent": {
            "contentType": "TEXT",
            "text": "cascade viber  --> whatsapp. No whatsapp content"
        }
    }
}'

Response:

{
    "title": "cascade-scheduling-request-not-valid",
    "status": 400,
    "detail": "Cascade scheduling request is not valid. Violations: the content was not found for the cascade template stage [cascadeTemplateId:31,634;stageUuid:6467a97d-c0b5-486b-9f94-733297b668de;channelType:WHATSAPP]"
}
Example 3. The content object has no channel parameters that are not included in the cascade, and has no channel parameters that are included in the cascade.

In the request below, only the viberContent and smsContent parameters are passed, even though the cascade with cascadeId = 31634 includes Viber and WhatsApp channels.

curl --location 'http://app.edna.io/api/cascade/schedule' \
--header 'Content-Type: application/json' \
--header 'x-api-key: **********' \
--data '{
    "requestId": "8bcb602f-ce61-4bce-a021-5dc52125a194",
    "cascadeId": 31634,
    "subscriberFilter": {
        "address": "+0000008000",
        "type": "PHONE"
    },
    "content": {
        "viberContent": {
            "contentType": "TEXT",
            "text": "cascade viber  --> whatsapp. No whatsapp content"
        },
        "smsContent": {
            "contentType": "TEXT",
            "text": "cascade viber  --> whatsapp. No whatsapp content"
        }
    }
}'

Response:

{
    "title": "cascade-scheduling-request-not-valid",
    "status": 400,
    "detail": "Cascade scheduling request is not valid. Violations: the content was not found for the cascade template stage [cascadeTemplateId:31,634;stageUuid:6467a97d-c0b5-486b-9f94-733297b668de;channelType:WHATSAPP]; the cascade template stage was not found for the content [cascadeTemplateId:31,634;contentChannelType:SMS]"
}

Receiving Message Status Errors

Errors during unsuccessful message delivery and receiving the undelivered status. For more information about receiving message statuses, see the article.

ErrorDescription
Not WhatsApp user.The recipient is not registered in WhatsApp. For WhatsApp channel only.
No match template.The message doesn’t match the registered templates.
Session not started.Session start error.
Daily rate limit.The daily template message limit exceeded. For WhatsApp channel only.
Too long message.The message length exceeds the allowed limit.
Chat window closed.Error opening the chat window. For WhatsApp channel only.
Media request failed.Error uploading a file.
Error subject unknown.The specified signature isn’t allowed. All signatures should be registered first.
Error address format.The format of the subscriber number is incorrect.
Duplicated.The message duplicate was attempted to be sent within 5 minutes.
In this article
In this article