There seems to be a problem today with /statuses/home_timeline when supplying both since_id and max_id to retrieve a range of tweets. I’m finding that the API is now returning an empty JSON array when both since_id and max_id are supplied. Is this a known issue, or intended change in behavior?
We began receiving reports from users related to this problem about 5 hours ago. The since_id and max_id combination is used in our application for filling timeline gaps.