/statuses/user_timeline max_id bug (returning tweet with id greater than request parameter)

api

#1

According the the REST API docs here: https://dev.twitter.com/rest/reference/get/statuses/user_timeline, the inclusion of the max_id request parameter “Returns results with an ID less than (that is, older than) or equal to the specified ID”. I’m witnessing a case where this does not hold.

Request 1 Parameters:
/statuses/user_timeline?screen_name=freeformtv&count=200&include_rts=true&exclude_replies=true

Response 1 Tweet IDs
{“id”:688028403690278900}
{“id”:688013297547898900}
{“id”:687998113949335600}

Following working with timelines logic suggested here: paging logic that is suggested here: https://dev.twitter.com/rest/public/timelines, the next request is made with max_id = (lowest Tweet ID returned - 1)

Request 2 Parameters (using last Tweet ID - 1)
/statuses/user_timeline?screen_name=freeformtv&count=200&include_rts=true&exclude_replies=true&max_id=687998113949335599

Request 2 Response Tweet IDs
{“id”:687998113949335600}

The ID returned is greater than the max_id requested.


#2

I am seeing the exact same thing. However, it seems to be intermittent. Sometimes it works as expected and sometimes not.

Is there any update to this issue?