Max_id parameter value to 99999999999999999999999 not working in all api calls

[TestChrysalis]

Hello, we are preparing our calls to the rest api for when the id of the tweets reaches the maximum. I’m passing 99999999999999999999999 to the max_id parameter. For example in the call https://api.twitter.com/1.1/search/tweets.json works while in the call https://api.twitter.com/1.1/statuses/user_timeline.json does not work.
Could you help me?
Thank you.

[andypiper]

Why would you be passing that value, except as as a test?

[TestChrysalis]

Because when you reach the maximum identifier of the tweet that is now an Int64 data, to be prepared without having to change our system

[CarlosChrysalis]

Hi andy, Can we know what is the greatest value that can be passed on to that call? That is, what is the max id we can ask to make that query?

[andypiper]

At this time, that information is not documented so we are not immediately able to comment. I wouldn’t expect values beyond the current max Tweet ID value to reliably work on that API call. As we move towards reaching a potential maximum, if there is an issue, we would announce plans on future handling.