# Continuous transformation is not update

**URL:** https://discuss.elastic.co/t/continuous-transformation-is-not-update/349212
**Category:** Elasticsearch
**Created:** [December 13, 2023, 4:06am UTC](https://discuss.elastic.co/t/continuous-transformation-is-not-update/349212 "2023-12-13T04:06:18Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Zosmex](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zosmex/32/129865_2.png) [@Zosmex](https://discuss.elastic.co/u/Zosmex)
#### Post date: [December 13, 2023, 4:06am UTC](https://discuss.elastic.co/t/continuous-transformation-is-not-update/349212/1 "2023-12-13T04:06:18Z")

</div>

I created a pivot continuous transformation to automatically count the data in each location. Each document has an **'updated\_at'** field which is a timestamp in epoch second format when each document was last modified.

After I updated many documents, I found that the created transformation had not updated its checkpoint, and documents in the destination index remained the same.

I also found that there are some ' **operations\_behind'** when I get statistics of the transformation.

```auto
"checkpointing": {
        "last": {
          "checkpoint": 1,
          "timestamp_millis": 1702437669083,
          "time_upper_bound_millis": 1702437609083
        },
        "operations_behind": 25868,
        "changes_last_detected_at": 1702437669081,
        "last_search_time": 1702438506413
      }

```

I'm not sure how continuous transformation updates itself. Maybe I missing something.

Hope anyone help

---

<div class="post-metadata">

### Author: ![GinkoLucas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ginkolucas/32/107055_2.png) [@GinkoLucas](https://discuss.elastic.co/u/GinkoLucas)
#### Post date: [December 13, 2023, 1:20pm UTC](https://discuss.elastic.co/t/continuous-transformation-is-not-update/349212/2 "2023-12-13T13:20:06Z")

</div>

Hello,

I came across a similar case, your documents may be indexed a little late, and when Transform checks for 'new' documents since the last checkpoint, it finds nothing. Wich date field do you use in your Transform for checking new fields ?

Try to increase the time between two checkpoints (Frequeny) to find out if you have this problem.

---

<div class="post-metadata">

### Author: ![Zosmex](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zosmex/32/129865_2.png) [@Zosmex](https://discuss.elastic.co/u/Zosmex)
#### Post date: [December 14, 2023, 2:03am UTC](https://discuss.elastic.co/t/continuous-transformation-is-not-update/349212/3 "2023-12-14T02:03:53Z")

</div>

Hi, GinkoLucas

I used field type 'date' in the format 'epoch\_second' that showed the last modified timestamp. I just changed 'frequency' to 5m, 15m, and 30m and still nothing happened except operation\_behind that keeps increasing.

Maybe this is because of wrong timestamp format?

---

<div class="post-metadata">

### Author: ![GinkoLucas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ginkolucas/32/107055_2.png) [@GinkoLucas](https://discuss.elastic.co/u/GinkoLucas)
#### Post date: [December 14, 2023, 8:34am UTC](https://discuss.elastic.co/t/continuous-transformation-is-not-update/349212/4 "2023-12-14T08:34:29Z")

</div>

When I read the documentation, I couldn't find any information about the date format. But it would be interesting to change it (or create a new field) and see if the Transform works.

---

<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: [January 11, 2024, 8:35am UTC](https://discuss.elastic.co/t/continuous-transformation-is-not-update/349212/5 "2024-01-11T08:35:21Z")

</div>

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