# Elasticsearch API for Javascript - Scroll

**URL:** <https://discuss.elastic.co/t/elasticsearch-api-for-javascript-scroll/42542>\
**Category:** Elasticsearch\
**Created:** [February 24, 2016, 12:51am UTC](https://discuss.elastic.co/t/elasticsearch-api-for-javascript-scroll/42542 "2016-02-24T00:51:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![James\_Tang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james_tang/32/8112_2.png) [@James\_Tang](https://discuss.elastic.co/u/James_Tang)\
**Post date:** [February 24, 2016, 12:51am UTC](https://discuss.elastic.co/t/elasticsearch-api-for-javascript-scroll/42542/1 "2016-02-24T00:51:27Z")

</div>

This is pertaining to the scroll API. I observed when scrolling and encountering an error, (In my case was a bad gateway , 502) , I will never get through the full population.

This observation tell me that, my request did reach elasticsearch and my scroll was forwarded to the next frame/page. Thus, I feel that as part of the scrolling, in addition to the scroll ID, the total frames/pages and the return frame id should be included. This will allow users to handle such skip.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:14pm UTC](https://discuss.elastic.co/t/elasticsearch-api-for-javascript-scroll/42542/2 "2017-07-05T23:14:03Z")

</div>