Skip to main content

We are facing an issue with the SMS API where messages are inconsistently delivered to the intended recipients. While the receiver did receive some messages previously, we've now encountered a scenario where messages are not being received at all. Interestingly, in such cases, we do not receive any error codes in the logs; the messageStatus is consistently shown as "Queued."


We've conducted troubleshooting efforts, including checking the RC inbox for any error signs or delivery issues, but everything appears to be functioning correctly from this end. Under normal circumstances, when using other services, if a message triggers a spam filter, it would at least be marked as "Undelivered." However, in our current situation, we're not observing any status changes that would indicate what happens after the message is queued.


Given that some messages were successfully received before, is there a way to monitor or track these messages more effectively to understand where the breakdown is occurring? Any advice on tools or methods provided by RingCentral for gaining deeper insights into message delivery statuses, especially for cases like this, would be greatly appreciated.


Thank you for your time and assistance.

I recommend you to submit a dev support ticket and provide your phone number, a few message ids of those messages stayed in "Queued" or even better to provide them with the API request id which you can get from each API call response header.


Reply