# Transforms on data older than a specific timestamp: checkpoints are not created

**URL:** https://discuss.elastic.co/t/transforms-on-data-older-than-a-specific-timestamp-checkpoints-are-not-created/296483
**Category:** Elasticsearch
**Tags:** transforms
**Created:** [February 7, 2022, 2:26pm UTC](https://discuss.elastic.co/t/transforms-on-data-older-than-a-specific-timestamp-checkpoints-are-not-created/296483 "2022-02-07T14:26:31Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Hendrik\_Muhs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hendrik_muhs/32/25802_2.png) [@Hendrik\_Muhs](https://discuss.elastic.co/u/Hendrik_Muhs)
#### Post date: [February 8, 2022, 7:39am UTC](https://discuss.elastic.co/t/transforms-on-data-older-than-a-specific-timestamp-checkpoints-are-not-created/296483/2 "2022-02-08T07:39:21Z")

</div>

Continuous mode is configured on a date field. The timestamp of that field is used for checkpointing. In your example `time_upper_bound_millis = 1644238440000` - which translates to `02/08/2022 @ 7:24am` in UTC is the time upper bound of the checkpoint. If you push data _before_ that time transform is not able to query for this data. That's by design.

Note the difference between `timestamp_millis` and `time_upper_bound_millis`. `time_upper_bound_millis` is calculating taking the system time, deducting `delay`. In this case the value is additionally rounded down to a bucket boundary, because you use a `date_histogram` in your transform configuration.

To workaround your problem you have 2 options:

- increase `delay`: if you increase `delay` to e.g. `6d` transform won't miss any data that arrives `now - 6d`, however it also won't process any data in between.
- use an [ingest timestamp](https://discuss.elastic.co/t/dec-12th-2018-en-elasticsearch-automatically-adding-a-timestamp-to-documents/159314) for sync: If you add another timestamp field in your source data which contains the date when the data has been ingested/indexed in Elasticsearch you can configure `sync` to use the ingest timestamp while you can still `pivot` on another timestamp field.

---

_[View the full topic](https://discuss.elastic.co/t/transforms-on-data-older-than-a-specific-timestamp-checkpoints-are-not-created/296483)._