When we interrogate the Search endpoint the search metadata field "next_results" is present in the first request response, but is missing afterwards.
Example:
1) first request is:
https://api.twitter.com/1.1/search/tweets.json?q=%23dallebimbeminkiahoimparatoche%20-RT&count=100
This returns "next_results" in "search_metadata" as such: "?max_id=364355058462228480&q=%23dallebimbeminkiahoimparatoche%20-RT&count=100&include_entities=1".
2) I then request:
https://api.twitter.com/1.1/search/tweets.json?max_id=364355058462228480&q=%23dallebimbeminkiahoimparatoche%20-RT&count=100&include_entities=1
I get the next 100 results, but "next_results" is missing.
I'm positive that there are "next results", in fact the same process in OAuth tool (https://dev.twitter.com/apps/012345/oauth) keeps returning a usable "next_results" field.