Inconsistent DirectMessage length error


#1

Hi,

We are testing sending DirectMessages using Twitter API (twitter4j). The same message, sometimes sent successfully and sometime comes back with message exceeded length error. After getting error, if we wait few minutes and try again, it goes successfully.

We would like to know why/where this inconsistency is? Do we need to subscribe for any policy setting for this account?

message:
Estimated restoral time of your a234567 services has been updated to 468. More details on a234567.com/outage.

[INFO ]pool-7-thread-1 2013-05-17 18:26:31,113 TwitterService - getInstance - Request Received
[INFO ]pool-7-thread-1 2013-05-17 18:26:31,113 TwitterService - sendMessage
[ERROR]pool-7-thread-1 2013-05-17 18:26:31,404 TwitterService - sendMessage - Failed to send a direct message:
403:The request is understood, but it has been refused. An accompanying error message will explain why. This code is used when requests are being denied due to update limits (https://support.twitter.com/articles/15364-about-twitter-limits-update-api-dm-and-following).
message - There was an error sending your message: Whoops! You already said that.
code - 151

Relevant discussions can be found on the Internet at:
http://www.google.co.jp/search?q=1ee4fdc3 or
http://www.google.co.jp/search?q=16eca9ab
TwitterException{exceptionCode=[1ee4fdc3-16eca9ab], statusCode=403, message=There was an error sending your message: Whoops! You already said that., code=151, retryAfter=-1, rateLimitStatus=null, version=3.0.3}
at twitter4j.internal.http.HttpClientImpl.request(HttpClientImpl.java:177)
at twitter4j.internal.http.HttpClientWrapper.request(HttpClientWrapper.java:61)
at twitter4j.internal.http.HttpClientWrapper.post(HttpClientWrapper.java:98)
at twitter4j.TwitterImpl.post(TwitterImpl.java:1871)
at twitter4j.TwitterImpl.sendDirectMessage(TwitterImpl.java:356)

Thanks for your support.