Sorry, you need to enable JavaScript to visit this website.

You are here

High rate of PEND status of messages

7 posts / 0 new
Last post

Matthew's picture
by Matthew

High rate of PEND status of messages
I am getting a high rate of messages staying in the PEND status when I go to check the status of messages. '/messages/sms/{messageId}/status' Some, if not all, of the messages have delivered and received succesfully. Is this due to the nature of SMS status reporting, or is it a deeper issue with the API? At the moment I am having to assume PEND is a success.

DeveloperSteve's picture
by DeveloperSteve

Hi Matthew, 

Hi Matthew, 

Try just sending the to: and body: as part of the api call.

Matthew's picture
by Matthew

I am only using to, from and
I am only using to, from and body. I am using from as I have a paid service with a dedicated number. I have not set the priority or validity of the messages.

DeveloperSteve's picture
by DeveloperSteve

Hi Matthew,

Hi Matthew,

Have you got a recent message ID stuck in pend that i can get the Messaging team to have a look at?

Matthew's picture
by Matthew

Here are 3 examples, for 3
Here are 3 examples, for 3 different numbers. d884f42e0e026c1f000000000046fd5c02c60201-1261470354332 d884d5bd000274460000000009086eae02c60201-1261408480972 d684d75d0006607e000000000b60c0b302c60601-1261400165866 ce83ff1700074bf8000000001cd389b302e50701-1261417285777 All sent on 14-15 February, I believe most if not all of the above examples were received by the receipients, please don't force these messages to send again.

DeveloperSteve's picture
by DeveloperSteve

Thanks Matthew, ive the

Thanks Matthew, ive the messageIds over so they can take a look see.

Will let you know the response as soon as i hear back. 

DeveloperSteve's picture
by DeveloperSteve

Hi Matthew, 

Hi Matthew, 

The messaging team has confirmed that the messaging Ids were delivered and the statuses indeed didnt update back on the message ids, from what they can see it looks like a timeout issue on the status being updated back into the database on the platform side. 

We have a fix going in place that will rectify this and make sure the status is update (or keep trying to update it). 

Thanks for flagging this.

Log in or register to post comments