Error Codes
Last updated:2026-03-10 10:48:28
Server Error Code
Note:
Unless a network error (such as 502 error) occurs, the HTTP return code of the push service REST API is 200.
Check the error code through ErrorCode and ErrorInfo in the response packet body, and refer to the following table.
Common error codes (60000 to 79999), see error code document.
Error Code | Description |
90001 | JSON format parsing failed. Check whether the request packet conforms to the JSON Specification. |
90005 | The JSON format request body lacks the MsgRandom field or the MsgRandom field is not of Integer type. |
90009 | The request requires App administrator permissions. |
90018 | Number of requested accounts exceeds the limit. |
90020 | The tag length exceeds the limit (must not exceed 50 bytes). |
90022 | Duplicate tags exist in the TagsOr and TagsAnd push conditions. |
90024 | Excessive frequency of push. The push interval must be greater than 1 second. |
90026 | Error in offline message storage time. |
90032 | The number of tags in the push condition exceeds 10, or the number of tags in the add tag request exceeds 10. |
90033 | Invalid attribute. |
90039 | Push by attribute and Tag Push cannot coexist. |
90040 | One of the push conditions has an empty tag. |
90045 | Push notification feature for all users/Tag/single push is not enabled. |
90047 | Push times exceed the daily limit (default: 100). |
90049 | Invalid TaskId returned, no push record. Push via the all users/Tag Push or single push API, and the TaskId returned can be used for withdrawal. |
90050 | Repeated withdrawal. Push tasks that have already been withdrawn cannot be called repeatedly. |
90051 | Withdrawal too frequent, withdrawal frequency limit is 1/s. |
90052 | The withdrawal validity period has expired. Withdrawal must be requested within 24 hours. Push tasks exceeding 24 hours cannot be withdrawn. |
90053 | Withdrawal unavailable. The push task is designated not stored on the roaming server/unread (OnlineOnlyFlag = 0), but OfflinePushInfo was not carried along during withdrawal. |
90056 | The request body for All Users Push is too large. Currently supports a maximum length of 10K. |
91000 | Internal Server Error, please retry. |
Client Error Code
Note:
Error Code | Description |
800001 | Register push service. The appKey parameter is invalid. |
800002 | Register push service. The sdkAppId parameter is invalid. |
800003 | Initialize SDK failed. |
800004 | Long link establishment failed. |
800005 | Push failure on local machine channel. |
800006 | Push failure on local machine channel, attempt FCM channel registration failed. |
800007 | Failed to detect ALL channels. |
800008 | Push service registration timeout. |
800009 | Push token is empty. |
800010 | Set token for SDK failed. |
800011 | Failed to disable automatic sign-up. |
800012 | Failed to disable push permission request. |
800013 | Failed to create notification channel. |
800014 | Failed to set push configuration. |
800015 | Experimental API call failure. |
800016 | User refused push pop-up permission. |
6014 | IM account not logged in, please log in first to register for push services. |
9523 | Please check whether the network is functioning properly. |
70016 | PublicKey does not exist. UserSig verification failed. Please confirm whether the correct appKey is used. |
Manufacturer Push Error Code
Note:
Here are common server error codes from manufacturers for reference. If you have any questions, consult the corresponding manufacturer.
Error Code | Description | Solution |
-1 | Unknown error | Contact Xiaomi technical support |
1 | Internal error | Contact Xiaomi technical support |
10001 | System error | Retry later; contact support if persistent |
10002 | System busy | Reduce request frequency; retry later |
10003 | Remote service error | Retry later |
10008 | Parameter error; refer to API docs | Check request parameters per API documentation |
10012 | Illegal request | Check request legitimacy |
10016 | Missing required parameter | Provide all required parameters |
10017 | Illegal parameter value | Check parameter value is within valid range |
10027 | API call too frequent for app | Reduce call frequency |
10029 | Invalid device (not found during register/unregister) | Check device registration status |
10030 | App fetches invalid regId too frequently | Reduce fetch frequency |
10031 | App is blacklisted; cannot send messages | Contact Xiaomi to remove from blacklist |
10032 | App fetches invalid alias too frequently | Reduce fetch frequency |
10033 | App is blacklisted for feedback requests | Contact Xiaomi to remove from blacklist |
10034 | Daily message quota exceeded | Reduce daily send volume; retry next day |
10035 | No more invalid aliases to pull | No action needed |
10036 | App operation is prohibited | Check app status; contact support |
10037 | Request expired | Check request timestamp; resend |
10038 | App prohibited from accessing statistics/trace data | Check permission configuration |
10039 | App fetches statistics/trace data too frequently | Reduce fetch frequency |
20607 | DB error | Retry later; contact support |
20209 | Invalid topic | Check topic format and content |
20215 | Topic subscription failed | Check if topic exists; retry later |
20216 | Topic unsubscription failed | Check if topic exists; retry later |
20301 | Message send failed | Retry later |
20315 | Broadcast message deletion failed | Retry later |
21301 | Authentication failed | Check authentication credentials (AppSecret etc.) |
21302 | Token authentication failed | Refresh token and retry |
21303 | Request throttled | Reduce request frequency |
21305 | Missing required parameter | Provide missing parameters |
22000 | Illegal app | Check app configuration and legitimacy |
22006 | Invalid app ID | Check if AppId is correct |
22007 | Invalid app key | Check if AppKey is correct |
22022 | Invalid app package name | Check if package name is correct |
22102 | Failed to send app notification message | Retry later |
26003 | Internal push call failed | Retry later |
26004 | Broadcast messages sent too frequently | Reduce broadcast frequency |
26005 | Account setting too frequent; blocked | Reduce account setting frequency |
26006 | Message requires review | Review message content promptly |
27001 | Channel information mismatch | Check channel configuration |
65003 | Device not found (usually offline) | Verify device online status |
65006 | Alias setting too frequent; blocked | Reduce alias setting frequency |
65007 | Alias is blacklisted | Change alias or contact support |
65008 | Alias too long | Shorten alias length |
65009 | Message content too long | Shorten message content |
65010 | Topic too long | Shorten topic length |
65011 | No parameters provided | Provide required parameters |
65012 | Alias is empty | Provide a valid alias |
65013 | Topic is empty | Provide a valid topic |
65014 | Too many key-value pairs | Reduce number of key-value pairs |
65015 | Key-value pairs total length too long | Shorten total length |
65016 | User account is empty | Provide a valid user account |
65017 | User account too long | Shorten user account length |
65028 | Message not found | Check if message ID is correct |
65029 | Remote service exception | Retry later |
65030 | Exception when building JSON | Check JSON format |
65035 | Too many topics | Reduce number of topics |
65036 | Callback parameter too long | Shorten callback parameter |
65037 | Callback URL too long | Shorten callback URL |
65038 | Callback URL is invalid | Check callback URL format |
65040 | Unregister failed | Retry later |
65041 | ImeiMd5 is empty | Provide a valid ImeiMd5 |
65042 | ImeiMd5 is invalid | Check ImeiMd5 format |
66006 | Registration failed (Android device error) | Check device registration flow |
66007 | Invalid regId format | Check regId format |
66008 | Illegal request | Check request legitimacy |
66108 | Invalid parameter info | Check parameter info |
66109 | Invalid regSecret | Check if regSecret is correct |
66300 | Unknown command | Check API endpoint and command name |
66301 | Command execution error | Retry later |
66303 | Xiaomi ID is empty | Provide a valid Xiaomi ID |
66304 | Xiaomi ID too long | Shorten Xiaomi ID |
66305 | Invalid Xiaomi ID format | Check Xiaomi ID format |
66306 | Failed to enable/disable push | Retry later |
66307 | Invalid message ID for scheduled job deletion | Check message ID |
66308 | Invalid rating service request parameters | Check request parameters |
70011 | Input is empty | Provide valid input |
70012 | Invalid JobKey format | Check JobKey format |
200001 | Daily push quota exceeded | |
200002 | Push QPS quota exceeded |
Error Code | Description | Solution |
-5 | Failed to get token task | |
502 | Connection error (unstable network) | |
503 | Traffic control | |
6003 | Certificate fingerprint mismatch | |
6004 | Permission not found during auth | |
80100003 | Message structure error | Check message structure params per response |
80100016 | Message contains sensitive words | Check message content |
80300002 | No permission to send to specified token | |
80300007 | Specified token is invalid | Different apps have different tokens; verify package name and AppID; check access_token URL; install/update HMS Core |
907122036 | Push service not enabled | |
907122046 | Push service unavailable | |
907122047 | General error code | |
907122054 | Push SDK auto-initializing; retry later | Install/update HMS Core from Huawei AppGallery |
907122069 | Sub-user operation not supported | Switch to device owner user |
907135000 | Invalid parameters | Check agconnect-services.json app_id/package_name; check build.gradle cert; reinstall HMS Core |
907135003 | SDK failed to connect HMS Core | HMS Core may have crashed; retry later; install/update HMS Core |
907135700 | Failed to query app scope via gateway | Check appid config; reinstall HMS Core; check Push enabled; check network |
907135701 | OpenGW Scope not configured |
Error Code | Description | Solution |
-1 | SERVICE_CURRENTLY_UNAVAILABLE | Retry later |
-2 | ERROR | Check local error details |
11 | Insufficient ISV Permissions | Check developer permissions |
12 | Http Action Not Allowed | Use correct HTTP method |
13 | App Call Limited | Reduce call frequency |
14 | Invalid App Key | Check AppKey parameter |
15 | Missing App Key | Provide AppKey parameter |
16 | Invalid Signature sign | Check if signature is correct |
17 | Missing Signature | Check signature parameter |
18 | Missing Timestamp | Check timestamp parameter |
19 | Invalid Timestamp | Check timestamp format |
20 | Invalid Method | Check if method name is correct |
21 | Missing Method | Provide method name parameter |
22 | Missing Version | Provide version parameter |
23 | Invalid Version | Version must be in numeric format |
24 | Unsupported Version | Use a supported version number |
25 | Invalid encoding | Use UTF-8 encoding for requests |
26 | IP Black List | Check if IP is blacklisted |
40 | Missing Required Arguments | Provide all required parameters per API docs |
41 | Invalid Arguments | Check parameter format and range |
Error Code | Description | Solution |
10000 | Auth failed / Unknown exception | Check authToken / Retry later |
10006 | Alias length exceeds 70 characters | Check alias length ≤ 70 |
10043 | Push channel closed for this app | Check push switch; contact vivo support |
10045 | App under review; cannot send formal messages | Send test messages; wait for approval |
10050 | Both alias and regId are empty | Provide at least alias or regId |
10051 | Unsupported classification type | Use 0 (operational) or 1 (system) |
10054 | Invalid notifyType | Use value 1-4 |
10055 | Title is empty | Provide title |
10056 | Title exceeds 40 characters | Shorten title ≤ 40 |
10057 | Content is empty | Provide content |
10058 | Content exceeds 100 characters | Shorten content ≤ 100 |
10059 | Invalid timeToLive | Set ≥ 60s, max 1 day |
10060 | Invalid skipType | Use value 1-4 |
10061 | skipType=2, skipContent is empty | Provide skipContent ≤ 2048 |
10062 | skipType=2, skipContent exceeds 2048 | Provide skipContent ≤ 2048 |
10063 | skipType=3, skipContent is empty | Provide skipContent ≤ 2048 |
10064 | skipType=3, skipContent exceeds 2048 | Provide skipContent ≤ 2048 |
10065 | Invalid networkType | Use -1 (any) or 1 (wifi only) |
10067 | Invalid custom key-value pairs | Total length ≤ 1024 chars |
10068 | skipType=4, skipContent is empty | Provide skipContent ≤ 2048 |
10069 | skipType=4, skipContent exceeds 2048 | Provide skipContent ≤ 2048 |
10070 | Operational message daily limit exceeded | See push limit rules |
10071 | Outside allowed send time range | See push time limit rules |
10072 | Push speed too fast | Increase push interval |
10073 | System message daily limit exceeded | Apply for unlimited system messages |
10082 | System message switch not enabled | Check system message switch; contact vivo support |
10092 | profileId length exceeds limit | profileId ≤ 64 chars |
10094 | AuthToken appId mismatch | Ensure authToken matches request appId |
10095 | Invalid notifyId | Value range: 1-2147483647 |
10096 | Invalid category | See category standard |
10097 | Category and classification mismatch | Ensure category matches classification |
10103 | Push content contains sensitive info | Check title and content |
10104 | Please send formal message | See push content limit rules |
10150 | Both aliases and regIds are empty | Provide at least one |
10151 | taskId is empty | Provide taskId from save group message API |
10152 | Invalid taskId | Create valid taskId via save group message API |
10153 | regIds count out of range [2-1000] | Adjust regIds count |
10154 | aliases count out of range [2-1000] | Adjust aliases count |
10155 | Message not found or expired | Recreate message via save group API |
10200 | appId is empty | Provide appId |
10201 | appKey is empty | Provide appKey |
10202 | Invalid appKey | appId and appKey mismatch; verify |
10203 | timestamp is empty | Provide timestamp |
10204 | sign is empty | Provide sign |
10205 | appId not found | Verify appId |
10206 | Invalid sign | Check sign generation |
10207 | Invalid timestamp | Use UTC timestamp within ±10min |
10252 | Batch message body limit exceeded | Daily batch API call limit reached |
10255 | Broadcast push API not available | Use tag push instead |
10301 | Alias exceeds 70 characters | Shorten alias ≤ 70 |
10302 | Invalid regId | Check regId status |
10304 | Extra contains unsupported key | Remove invalid keys from extra |
10305 | Extra callback length exceeds limit | callback ≤ 128 chars |
10306 | Extra callback.param length exceeds limit | callback.param ≤ 192 chars |
10307 | Invalid alias | Alias may have expired |
10311 | Device currently unable to push | Check notification permission and device activity |
10352 | requestId is empty | Provide requestId |
10353 | requestId exceeds 64 characters | Shorten requestId ≤ 64 |
10471 | taskIds count exceeds 100 | Max 100 taskIds per request |
10472 | Invalid taskIds format | Comma-separated taskIds, max 100 |
10473 | taskIds is empty | Provide taskIds |
10600 | Invalid name parameter | Use Chinese/English/digits/underscores, not starting with digit, ≤ 50 |
10601 | Tag name is empty | Provide tag name |
10602 | Tag description exceeds 300 characters | Shorten description ≤ 300 |
10603 | oldName is empty | Provide oldName |
10604 | newName is empty | Provide newName |
10605 | Invalid oldName | Use valid naming format ≤ 50 |
10606 | Invalid newName | Use valid naming format ≤ 50 |
10608 | type parameter is empty | Provide type |
10609 | ids parameter is empty | Provide ids |
10610 | Tag name already exists | Change name and retry |
10611 | Tag category name already exists | Change name and retry |
10612 | Tag combination name already exists | Change name and retry |
10613 | Invalid group parameter | Use valid naming format ≤ 50 |
10614 | ids count exceeds 1000 | Limit ids ≤ 1000 |
10615 | tag count exceeds 100 | Limit tags ≤ 100 |
10616 | Invalid type parameter | Use 1 (normal) or 2 (exclusive) |
10700 | userids is empty | Provide userids |
10701 | userid count exceeds limit | Reduce userid count |
10703 | Rate limit exceeded | Retry later |
10704 | requestId exceeds 64 characters | Shorten requestId ≤ 64 |
10706 | Invalid userType | Use 1 (regId) or 2 (alias) |
10800 | registration_tokens count out of range | Max 100 |
10801 | notification is empty | Provide notification |
10802 | original_source_name is empty | Provide original_source_name |
10803 | original_source_name length exceeds limit | ≤ 128 chars |
10804 | original_source_ip is empty | Provide original_source_ip |
10806 | Invalid click_action | url and intent cannot both be empty |
10807 | url length exceeds limit | ≤ 1024 chars |
10808 | intent length exceeds limit | ≤ 1024 chars |
Error Code | Description | Solution |
40000003 | Target app not installed | Clean up this token |
40000004 | Token invalid or not exist for terminal user | Check token validity; user may have cleared data/reinstalled |
40000005 | App notification switch off | Guide user to enable notification |
40000006 | Target app disabled or stopped on device | Check app status |
40000007 | Notification clicked | N/A (normal status) |
40000009 | Message discarded by system (may exceed quota) | Adjust volume; see message quota rules |
40000011 | Notification jump to page failed (page missing or no permission) | Check target page exists and has permission |
40000013 | Notification throttled (screen-off power saving) | Message re-delivered when screen on |
40000014 | Token user mismatch with device current user | Check token corresponds to current device user |
40000015 | Notification display failed; discarded (Intent error / display limit) | Check Intent config; control notification count |
50000003 | App process not running; passthrough msg cached | Cached until app starts |
400 | Parameter error | Check response error code for details |
403 | Authentication failed | Check if Access Token is correct |
404 | Service not found | Check if request URI is correct |
500 | Internal server error | Check request format matches docs; contact honorpush@honor.com |
502 | Connection error (unstable network) | Retry later |
503 | Too many requests; QPS limit exceeded (3000/app) | Retry later |
80100000 | Partial tokens sent successfully | Check failTokens in response |
80100003 | Message structure error | Check message structure params per response |
80300006 | Push Token is repeat | Check for duplicate Push Tokens |
80300007 | All Push Tokens are invalid | Verify app package/ID match; check access_token/send URL |
80300008 | Message body exceeds default limit (4096B) | Reduce message body size |
80300010 | Push Token count exceeds 1000 per request | Check Push Token count ≤ 1000 |
80200020 | Receipt ID mismatch | Check receiptId |
80200022 | No permission to send this message type | Check if image field is used in marketing message (only for service messages) |
80200047 | Test message daily limit reached | Send formal message or try next day |
80200050 | Marketing message does not support image field | Remove image field from marketing messages |
80200056 | Message title/content contains sensitive info | Check message title and content |
10001 | Timestamp is null | Check timestamp |
10207 | Timestamp is invalid | Get valid timestamp and verify |
10300 | Push Token is null | Provide Push Token |
10205 | AppId not found | Check appId |
Error Code | Description | Solution |
100000 | Other types of errors | Refer to the specific error message for details. |
100001 | Invalid APNs certificate or Auth Key | Check if the APNs certificate or Auth Key is valid. |
100002 | Invalid parameters in request | Verify that the request parameters are correct. |
100003 | Rate limit exceeded for a single device | Reduce the message sending frequency. |
100004 | Certificate mismatch | Ensure the correct certificate is being used. |
100005 | Device token not found | Check if the device token is valid and active. |
100006 | Service temporarily unavailable | Please try again later. |
Error Code | Description | Solution |
400 | BadCollapseId:The collapse identifier exceeds the maximum allowed size. | Check collapse_id length limit |
400 | BadDeviceToken: The specified device token is invalid. Verify that the request contains a valid token and that the token matches the environment. | Verify valid token and environment match |
400 | BadExpirationDate: The apns-expiration value is invalid. | Check apns-expiration value format |
400 | BadMessageId: The apns-id value is invalid. | Check apns-id value format |
400 | BadPriority: The apns-priority value is invalid. | Check apns-priority is valid |
400 | BadTopic: The apns-topic value is invalid. | Check apns-topic value |
400 | DeviceTokenNotForTopic: The device token doesn’t match the specified topic. | Verify device token matches topic |
400 | DuplicateHeaders: One or more headers are repeated. | Check for duplicate request headers |
400 | IdleTimeout: Idle timeout. | Check connection keepalive; reconnect |
400 | InvalidPushType: Theapns-push-typevalue is invalid. | Check apns-push-type value |
400 | MissingDeviceToken: The device token isn’t specified in the request:path. Verify that the:pathheader contains the device token. | Verify :path header contains device token |
400 | MissingTopic: Theapns-topicheader of the request isn’t specified and is required. Theapns-topicheader is mandatory when the client is connected using a certificate that supports multiple topics. | Add apns-topic header (required for multi-topic certs) |
400 | PayloadEmpty: The message payload is empty. | Ensure payload is not empty |
400 | TopicDisallowed: Pushing to this topic is not allowed. | Check topic push permission |
403 | BadCertificate: The certificate is invalid. | Check APNs certificate validity |
403 | BadCertificateEnvironment: The client certificate doesn’t match the environment. | Match certificate with push environment (dev/prod) |
403 | ExpiredProviderToken: The provider token is stale and a new token should be generated. | Generate a new provider token |
403 | Forbidden: The specified action is not allowed. | Check operation permission |
403 | InvalidProviderToken: The provider token is not valid, or the token signature can’t be verified. | Verify provider token validity and signature |
403 | MissingProviderToken: No provider certificate was used to connect to APNs, and theauthorizationheader is missing or no provider token is specified. | Add provider cert or authorization header |
403 | UnrelatedKeyIdInToken: The key ID in the provider token isn’t related to the key ID of the token used in the first push of this connection. To use this token, open a new connection. | Open new connection for this token |
403 | BadEnvironmentKeyIdInToken: The key ID in the provider token doesn’t match the environment. | Match key ID with push environment |
404 | BadPath: The request contained an invalid:pathvalue. | Check request path |
405 | MethodNotAllowed: The specified:methodvalue isn’tPOST. | Use POST method |
410 | ExpiredToken: The device token has expired. | Clean up device token; wait for re-registration |
410 | Unregistered: The device token is inactive for the specified topic. There is no need to send further pushes to the same device token, unless your application retrieves the same device token, refer to[Registering your app with APNs](/documentation/usernotifications/registering-your-app-with-apns) | Stop pushing unless app retrieves same token |
413 | PayloadTooLarge: The message payload is too large. For information about the allowed payload size, refer to Create a POST request to APNs in[Sending notification requests to APNs](/documentation/usernotifications/sending-notification-requests-to-apns). | Reduce payload size |
429 | TooManyProviderTokenUpdates: The provider’s authentication token is being updated too often. Update the authentication token no more than once every 20 minutes. | Update auth token at most once per 20 minutes |
429 | TooManyRequests: Too many requests were made consecutively to the same device token. | Reduce request frequency to same device token |
500 | InternalServerError: An internal server error occurred. | Retry later |
503 | ServiceUnavailable: The service is unavailable. | Retry later |
503 | Shutdown: The APNs server is shutting down. | Retry later; wait for service recovery |
Error Code | Description | Solution |
500 | Other exception | Retry later; contact Meizu technical support if persistent |
1001 | System error | Internal server exception; retry later; contact Meizu support if frequent |
1003 | Server busy | Server overloaded; reduce request frequency; retry later |
1005 | Parameter error; refer to API docs | Check request parameters per API docs; verify field names and formats |
1006 | Signature authentication failed | Check appKey/appSecret; verify signature algorithm matches docs |
110000 | Invalid AppID | Verify AppID is correctly registered on Meizu push platform |
110001 | Invalid appKey | Verify appKey matches Meizu platform; check if expired or reset |
110002 | pushId expired (not subscribed) | Clean up invalid pushId; re-obtain device pushId |
110003 | Invalid pushId | Check pushId source and format |
110004 | Parameter cannot be empty | Check required fields are not empty; ensure pushId/alias/title/content are provided |
110005 | Alias expired (not subscribed or notification switch off) | Alias not subscribed or user disabled notification; check alias binding; guide user to enable notification |
110009 | App is blacklisted | App banned for violation; check content compliance; contact Meizu to appeal |
110010 | Push rate too fast / pushId expired (notification switch off) | Reduce push frequency per Meizu rate limit; or check device notification switch; guide user to enable notification |
110053 | Passthrough message limit exceeded | Passthrough message quota exceeded; reduce frequency or switch to notification |
201 | No permission; server rejected | Check push permission enabled; verify appKey and appSecret are valid |
501 | Push message failed (db_error) | Server DB error; retry later; contact Meizu support if persistent |
513 | Push message failed | General push failure; check message format and parameters; retry later |
519 | Push message failed due to service overload | Server overloaded; reduce send rate; implement backoff retry strategy |
520 | Message collapsed (same device same app received multiple times within 1 min; default 5) | Too many messages to same device collapsed; merge messages or reduce push frequency per device |
Manufacturer Receipt Error Code
Note：
This section lists only the common error codes during the receipt phase for various manufacturers for reference. If you have any questions, please consult the respective manufacturer directly.
Documentation links for Push Service error codes: Xiaomi/ Huawei / VIVO / Honor / OPPO. Note that for Huawei and Honor, you must complete the manufacturer receipt configuration manually.
Google FCM and Apple APNs protocols do not natively support manufacturer receipt mechanisms.
Error Code | Description | Solution |
16 | Invalid target device (offline >30 days / invalid alias/account/regID / app unregistered or uninstalled / wrong target region) | Filter out invalid users; reduce ineffective pushes |
32 | Client called disablePush to disable push | Stop pushing to this device |
64 | Target device does not meet filter criteria (network/location/app version/model/region/language mismatch) | Check push condition filter settings |
128 | Daily push total or per-device limit exceeded | |
1024 | Message TTL expired | Adjust message TTL; or speed up push delivery |
Error Code | Description | Solution |
2 | App not installed | App uninstalled after delivery; clean up this token |
5 | Specified token does not exist for current Android user | Investigate: user cleared app data / reinstalled / called deleteToken / factory reset / app not activated / sub-user deleted |
6 | Notification not displayed | Investigate: turnOffPush called / user disabled system notification switch / user disabled app notification channel |
10 | Inactive device | Device offline for 30+ days; message not delivered; clean up this token |
14 | Other error | Internal system network error; retry later |
15 | Offline user message throttled | Message overwritten due to collapse_key / offline cache exceeds 120; old messages replaced |
22 | UserID mismatch | Multi-user scenario: userID in message doesn't match current user; check userID |
27 | Target app process not running; passthrough message cached | App process not running and auto-start disabled; passthrough message cached |
31 | System version or app does not support this message | Check if app supports message (Intent page missing / activity permission / exported=false); upgrade push service |
51 | Device powered on but screen locked | User rebooted but hasn't unlocked; message delivered after unlock |
102 | Message discarded due to frequency control | Max 3000 messages per device per app per day; wait until next day |
144 | ProfileId does not exist | Check profile_id field when sending downstream message |
201 | Message delivery throttled by server | Push server blocked message; possible: token-user mismatch / notification disabled / app uninstalled; check subStatus |
256 | Info/marketing message frequency limit | Daily quota exceeded; adjust strategy / notification rules violated |
Error Code | Description | Solution |
1 | regid_invalid: regid invalid | Developers can prune or filter invalid RegistrationIDs after receiving the event callback to improve push efficiency. |
1 | user_daily_limit: user daily limit | After receiving the 'Daily Quota Exceeded per App per Device' event callback, developers can optimize their push strategies to minimize redundant delivery attempts. |
Error Code | Description | Solution |
100 | subAckType=11001: Throttled - push volume exceeded | Reduce push volume |
100 | subAckType=12000: Throttled - per-app per-user frequency limit | Reduce push frequency per user |
100 | subAckType=10012: Throttled - message expired | Check message TTL settings |
100 | subAckType=14002: Throttled - device offline during online direct push; discarded | Device offline; use offline message |
100 | Throttled - other (outside push time / version unsupported etc.) | Check push time and version requirements |
101 | Message failed content review | Check title/content compliance |
102 | subAckType=20001: Mismatch - user not subscribed | Confirm user subscribed to push |
102 | subAckType=20002: Mismatch - user does not exist | Confirm regId or alias is valid |
102 | subAckType=20006: Mismatch - inactive device | Device offline long-term; clean up invalid tokens |
102 | Mismatch - other | Check if push target is valid |
103 | Offline message overwritten | Reduce offline message frequency; adjust override strategy |
104 | subAckType=1017: Not displayed - operational msgs hidden 23:00-07:00 | Adjust push time to avoid nighttime |
104 | subAckType=2124: Not displayed - duplicate title/content operational msg (1 per user per day) | Avoid duplicate title/content to same user |
104 | subAckType=2144: Not displayed - message expired | Adjust message TTL settings |
104 | subAckType=2158: Not displayed - deeplink parameter error | Check deeplink parameter format |
104 | subAckType=2161: Not displayed - target activity not exported | Set target activity exported=true |
104 | subAckType=2162: Not displayed - target activity not found | Check if target activity exists |
104 | subAckType=2183: Not displayed - regId expired | Re-obtain regId from client |
104 | subAckType=2333: Not displayed - app from non-official channel has operational msg disabled by default | See message restriction docs |
104 | Not displayed - other | Check notification switch and channel settings |
Error Code | Description | Solution |
40000003 | Target app not installed | Clean up this token |
40000004 | Token invalid or not exist for terminal user | Check token validity; user may have cleared data/reinstalled |
40000005 | App notification switch off | Guide user to enable notification |
40000006 | Target app disabled or stopped on device | Check app status |
40000007 | Notification clicked | N/A (normal status) |
40000009 | Message discarded by system (may exceed quota) | Adjust volume; see message quota rules |
40000011 | Notification jump to page failed (page missing or no permission) | Check target page exists and has permission |
40000013 | Notification throttled (screen-off power saving) | Message re-delivered when screen on |
40000014 | Token user mismatch with device current user | Check token corresponds to current device user |
40000015 | Notification display failed; discarded (Intent error / display limit) | Check Intent config; control notification count |
50000003 | App process not running; passthrough msg cached | Cached until app starts |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback