# How the continuous transform job skip the already read document from an index

**URL:** https://forum.opensearch.org/t/how-the-continuous-transform-job-skip-the-already-read-document-from-an-index/18691
**Category:** Index Management
**Created:** [April 3, 2024, 2:18pm UTC](https://forum.opensearch.org/t/how-the-continuous-transform-job-skip-the-already-read-document-from-an-index/18691 "2024-04-03T14:18:31Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![adarshmohan1](https://avatars.discourse-cdn.com/v4/letter/a/eb9ed0/32.png) [@adarshmohan1](https://forum.opensearch.org/u/adarshmohan1)
#### Post date: [April 3, 2024, 2:18pm UTC](https://forum.opensearch.org/t/how-the-continuous-transform-job-skip-the-already-read-document-from-an-index/18691/1 "2024-04-03T14:18:31Z")

</div>

implemented **Versions** (relevant - OpenSearch/Dashboard/Server OS/Browser):  
OpenSearch 2.9.0

**Describe the issue** :  
I have created a transform job which is continuously running in every hour. There is no range filter added in the data\_selection\_query, so that it will read all the documents in the index. Will this transform job read and aggregate the already read document from the index when it run for the sencond time? If no, how the transform job is tracking the already read document? Are we saving the state of documents any where?

**Configuration** :

**Relevant Logs or Screenshots** :

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/3/33547ea01a5b12dcca2958411d3edd97ae2ea8c1.png) [@system](https://forum.opensearch.org/u/system)
#### Post date: [June 2, 2024, 2:18pm UTC](https://forum.opensearch.org/t/how-the-continuous-transform-job-skip-the-already-read-document-from-an-index/18691/2 "2024-06-02T14:18:37Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.