Guides

Errors

Under this area you can quickly find all the errors your application generates. You will mostly find here errors related with APNS or GCM/FCM authentication, messages that coupld not be delivered and devices that no longer exist.

In any of your apps you'll find a menu item called Errors as follows:

Menu 7b8901c757

If your application has generated errors you can find them in a list as the one below:

List 3ccb0aab93

Because these errors are merely informative, you can at any moment clear this list by using the Options menu in the top right corner and clicking in Clear All:

Options clear all 59fbe24b83

Below you'll find the list of possible errors for each platform:

Apple Push Notifications Errors

Common errors found when sending messages via APNS.

System errors

ErrorDescription
Processing errorThe system could not process the message
Missing device tokenThe system could not process the message due to a missing device token
Missing topicThe system could not process the message due to a missing topic (bundle ID)
Missing payloadThe system could not process the message due to a missing message payload
Invalid token sizeThe system could not process the message because device token has an invalid size
Invalid topic sizeThe system could not process the message because topic has an invalid size
Invalid payload sizeThe system could not process the message because payload has an invalid size
Connection terminatedThe system could not process the message because connection to APNS was terminated

Delivery errors

ErrorDescription
Invalid tokenThe system tried to send a message to a device token that was not registered for this app. The device was deactivated.
Received feedback for tokenFeedback service notified that the device token uninstalled the app. The device was deactivated.

Setup errors

ErrorDescription
Retry limit exceededThe system failed to deliver a message after several retries
Connection error, possibly wrong certificateThe system failed to deliver a message because the certificate is invalid or for a different app
Connection error, possibly revoked certificateThe system failed to deliver a message because the certificate is no longer valid or revoked

Misc. errors

ErrorDescription
Unknown errorThe system got an unknown error and could not process the message

Google Cloud Messaging/Firebase Cloud Messaging Errors

Common errors found when sending messages via GCM/FCM.

System errors

ErrorDescription
GCM unavailableThe system failed to connect to GCM/FCM because the service is unavailable
Connection errorThe system failed to connect to GCM/FCM due to a network error

Setup errors

ErrorDescription
Authentication errorThe system failed to connect to GCM/FCM due to a wrong Server Key

Delivery errors

ErrorDescription
Device is unavailableThe system tried to deliver a message but the device was not available at that time
Device is not registeredThe system tried to deliver a message to a device token that was not registered for this app. The device was deactivated.

Misc. errors

ErrorDescription
Unknown errorThe system got an unknown error and could not process the message

Web Push Notifications Errors

Common errors found when sending web push notifications via GCM, Safari Web Push and VAPID.

System errors

ErrorDescription
Failed after retriesThe system tried to deliver a message several time and failed to deliver it.

Delivery errors

ErrorDescription
Device is not registeredThe system tried to send a notification to a token that was not registered for this website. The device was deactivated.

Setup errors

ErrorDescription
Invalid payload or authentication mismatchSystem could not connect to VAPID (probably wrong VAPID)
Authentication errorSystem could not connect to VAPID or GCM (most likely wrong VAPID or device auth key)

Misc. errors

ErrorDescription
Unknown errorThe system got an unknown error and could not process the message

Email Errors

Common errors found when sending email messages via our SMTP servers.

System errors

ErrorDescription
Insufficient email creditThe message could not be sent because there was not enough email credit on the account balance
Message rejectedThe message could not be sent because of missing or invalid recipient
Service unavailableThe message could not be sent due to a temporary failure of the server
Error sending messageThe message could not be sent for reasons other than the ones described here

Delivery errors

ErrorDescription
Recipient was suppressedThe recipient's email address is on the suppression list because it has a recent history of producing hard bounces. The recipient was deactivated.
Recipient does not existThe intended recipient's email provider sent a bounce message indicating that the email address doesn't exist. The recipient was deactivated.
Recipient not acceptedThe recipient's email provider sent a hard bounce message, but didn't specify the reason for the hard bounce. The recipient was deactivated.
Recipient mailbox is fullThe recipient's email provider sent a bounce message because the recipient's inbox was full. You might be able to send to the same recipient in the future when the mailbox is no longer full.
Message too largeThe recipient's email provider sent a bounce message because message you sent was too large. You might be able to send a message to the same recipient if you reduce the size of the message.
Content rejectedThe recipient's email provider sent a bounce message because the message contained an unacceptable attachment. For example, some email providers may reject messages with attachments of a certain file type, or messages with very large attachments. You might be able to send a message to the same recipient if you remove or change the content of the attachment.
Attachment rejectedThe recipient's email provider sent a bounce message because the message you sent contains content that the provider doesn't allow. You might be able to send a message to the same recipient if you change the content of the message.
Reason unknownThe recipient's email provider sent a bounce message. The bounce message didn't contain enough information to determine the reason for the bounce.
Received complaint: AbuseIndicates unsolicited email or some other kind of email abuse. The recipient was deactivated.
Received complaint: Auth-FailureEmail authentication failure report
Received complaint: FraudIndicates some kind of fraud or phishing activity. The recipient was deactivated.
Received complaint: OtherIndicates any other feedback that does not fit into other registered types. The recipient was deactivated.
Received complaint: VirusReports that a virus is found in the originating message

Setup errors

ErrorDescription
Sender domain not verifiedThe message could not be sent because the MX record required to use the specified sender domain could not be verified

SMS Errors

Common errors found when sending SMS messages via our system.

System errors

ErrorDescription
Insufficient sms creditThe message could not be sent because there was not enough SMS credit on the account balance
Queue overflowYou tried to send too many messages too quickly, and your message queue overflowed. Try sending your message again after waiting for some time.
Unknown destinationThe destination number you are trying to reach is unknown and may no longer exist.
Unreachable carrierThe destination number is unable to receive this message. Potential reasons could include trying to reach a landline or an unreachable carrier.
Error sending messageThe error does not fit into any of the above categories

Delivery errors

ErrorDescription
Unreachable destinationThe destination handset you are trying to reach is switched off or otherwise unavailable.
Message blockedThe destination number you are trying to reach is blocked from receiving this message (e.g., due to blacklisting)
Carrier violationYour message was flagged as objectionable by the carrier. To protect their subscribers, many carriers have implemented content or spam filtering.
Error delivering messageThe error does not fit into any of the above categories