# Can we expand scroll request timeout (Java API)? **URL:** https://discuss.elastic.co/t/can-we-expand-scroll-request-timeout-java-api/57696 **Category:** Elasticsearch **Created:** [August 10, 2016, 11:41am UTC](https://discuss.elastic.co/t/can-we-expand-scroll-request-timeout-java-api/57696 "2016-08-10T11:41:24Z") **Posts on this page:** 1 **Showing post:** 5
### Author: ![Akita](https://avatars.discourse-cdn.com/v4/letter/a/ecc23a/32.png) [@Akita](https://discuss.elastic.co/u/Akita) #### Post date: [August 11, 2016, 8:17am UTC](https://discuss.elastic.co/t/can-we-expand-scroll-request-timeout-java-api/57696/5 "2016-08-11T08:17:20Z")
In my own experience, my scroll Id do not always change, especially during the first calls (but calling them again following the "call the last" rule do parse the next scroll). I ran SHA1 on them and even char-to-char comparison to be sure that they were identical and not just alike. Mooky ([Scroll Questions](https://discuss.elastic.co/t/scroll-questions/18163/1) , question 4) and Sujoysett ([Do unique/reusable \_scroll\_ids exist?](https://discuss.elastic.co/t/do-unique-reusable--scroll-ids-exist/12280/3)) seem to have experienced the same situation. I know the ID is related to shards and/or their state, but I don't know the details. But in my case, it doesn't always change. Example below: 1)I run the first request, asking for a new scroll context. Result on the right panel: Some docs and an ID. ![](https://us1.discourse-cdn.com/elastic/original/2X/3/35cfc06506bd95885ec0deb5337f7bfc18b61799.png)\> 1. Then I copy/paste the ID in the body of the second request, and execute. I got some different doc, but same id. (Verified "manually", on [https://www.diffnow.com/](https://www.diffnow.com/), and same sha1) ![](https://us1.discourse-cdn.com/elastic/original/2X/d/d1850f14ea59c80fabac1760d13ace3b7cdb7a74.png) So my questions remain :). --- _[View the full topic](https://discuss.elastic.co/t/can-we-expand-scroll-request-timeout-java-api/57696)._