RCS Error Code - FAQ’S
RCS Error Code - FAQ’S
MSG91 PANEL
ERROR | Why This Happens | How to Fix It |
Unreachable Number | RCS Not Enabled on Device, Number Format Issue, Device Offline / No Data, Temporary Network Issue | Ensure proper formatting https://msg91.com/help/rcs/new-article-1724395069894781 , Add fallback channels (sms, email, whatsapp) https://msg91.com/help/campaign/how-to-create-a-campaign-flow |
Image provided is greater than maximum limit | RCS Image Size Limits - | Resize the Dimensions as https://msg91.com/help/rcs/rcs-create-template-with-validations |
Invalid Number | Number Format Issue, Fake or Test Numbers, Number Not Registered for RCS, Blocked or Inactive Number | Always Use country code before number, Add fallback channels (sms, email, whatsapp) https://msg91.com/help/campaign/how-to-create-a-campaign-flow |
Too many requests | Rate Limit Exceeded | Send only 4 RCS templates to each user per month https://msg91.com/help/rcs/rcs-create-template-with-validations |
User not found | Recipient is not RCS-enabled, Using iOS or Unsupported Device, Temporary Network/Registration Issue, Number Issue | It means users not having RCS enabled in their mobile phone. |
Opted out customer | User blocked the brand agent, User opted out of promotional messages, Consent not taken or expired, Google RBM policy violation | Check if the user is on the OPTOUT list to receive RCS messages. If you want to send messages, remove the number from the Blacklist Number list https://msg91.com/help/rcs/how-to-set-opt-out-rules-in-rcs- |
API
Http Code | Massages | Code | Why This Happens | How to Fix It |
400 | Bad request | 2 | Invalid JSON Payload, Wrong Parameter Names, Empty or Missing Required Fields, Invalid URL | Validate JSON Payload, Ensure Media URLs, Check Headers |
401 | Unauthorized | 3 | Invalid or Expired Access Token, Missing Authorization Header, Wrong API Key or Credentials | Regenerate Access Token, Check API Key |
402 | Forbidden | 4 | Wrong Project / Brand Mapping, Agent Not Approved or Not Live | Check Agent Status, Verify Token and Project |
404 | User Not found | 5 |
| Check RCS Capability Before Sending, Use Correct Number Format, Enable Fallback Messaging |
429 | Too many requests | 6 | Exceeding API Rate Limit, | Implement a Queue, Check Provider Limits |
500 | Internal Server Error | 7 | Temporary network disruptions, API server overload, DNS or routing failures | Check your internet connectivity, Ensure API endpoint is reachable and not under maintenance |
429 | Bot Rate Limit Exceeded | 9 | Sending too many messages in a short period (bulk campaign without throttling), Improper batching or queuing mechanism, Multiple retries fired simultaneously | Implement retry logic with exponential backoff when this error occurs, Contact your provider to request higher rate limits if needed |
500 | Internal Server Error | 11 | Slow network connectivity, Server overload or high latency, API processing delay | Ensure you have a stable internet connection, Implement timeout and retry logic with exponential backoff, If the issue persists, check server status or contact support |
500 | Internal Server Error | 12 |
| Retry the request after some time, Check your network connectivity, Contact your service provider if the issue persists |
500 | Internal Server Error | 13 |
| Retry the request after some time, Check your network connectivity, Contact your service provider if the issue persists |
500 | Internal Server Error | 14 | | Retry the request after some time, Check your network connectivity, Contact your service provider if the issue persists |
400 | Invalid value for message, one of fields for expiry is already set | 15 | Wrong field name or incorrect data type in the payload, Duplicate message parameters in the request body | Validate the payload structure as per RCS API documentation, Ensure correct data type |
400 | Invalid value for message field expiry time. | 16 | Expiry time is set in the past or exceeds the maximum allowed duration. Negative or non-numeric value is provided. Incorrect field name or extra parameters in the request. | Ensure expiry time is future-dated and within the allowed limit, Remove any conflicting expiry fields |
400 | Invalid value for message field ttl, the ttl duration must a digit string ending with 's' | 17 | TTL is missing the unit ‘s’ (seconds) at the end, TTL contains invalid characters or spaces, TTL exceeds maximum allowed duration | Ensure TTL value does not exceed 14 days, Validate your JSON payload format before sending. |
500 | Internal Server Error | 20 | Temporary network or server issues, The user’s carrier or device did not respond to the capability check, API timeout or upstream service failure | Retry the request after some time, Ensure you have a stable internet connection, Validate that the phone number |
500 | Internal Server Error | 21 | Missing or incorrect fields in the request body, Unsupported media format or size, Invalid phone number format | Validate the message payload against the API documentation, Ensure media files meet RCS requirements, Check your authentication token and regenerate if needed |
403 | Operation not allowed. Account inactive | 23 | Account not yet approved or verified by Google RBM, Account suspended due to policy violation or inactivity, Billing or subscription issues with the RCS provider | Complete any pending verification or approval steps, Resolve billing or compliance issues, If account was suspended, contact support to reactivate it |
403 | Operation not allowed. User has opted out. | 24 | User blocked your brand or replied with STOP, Consent expired or was revoked, Sending promotional messages without proper opt-in | Provide a clear opt-in mechanism via SMS, email, or website, Maintain an updated opt-out suppression list in your system |
500 | Internal Server Error | 25 | Missing or incorrect fields in the request body, Unsupported media format or size, Invalid phone number format | Validate the message payload against the API documentation, Ensure media files meet RCS requirements |
500 | Too many requests! Account configured TPS exceeded/ | 28 | Bulk campaigns sending messages too quickly, No throttling or queuing implemented, Multiple concurrent API calls exceeding account quota | Contact your provider to increase TPS limits if needed, Monitor your campaign flow and adjust scheduling to avoid bursts |
500 | Internal Server Error | 30 | Corrupted or incomplete assistant configuration, Missing required parameters during creation, Network or server connectivity issues during setup. | Re-create the assistant with all mandatory configuration fields, Verify your authentication credentials and permissions, Ensure a stable network connection during setup |