# Elastic Latest Transform is not working if sync time and sort time is different

**URL:** <https://discuss.elastic.co/t/elastic-latest-transform-is-not-working-if-sync-time-and-sort-time-is-different/355001>\
**Category:** Kibana\
**Tags:** transforms\
**Created:** [March 8, 2024, 4:20am UTC](https://discuss.elastic.co/t/elastic-latest-transform-is-not-working-if-sync-time-and-sort-time-is-different/355001 "2024-03-08T04:20:29Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![greco](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/greco/32/106815_2.png) [@greco](https://discuss.elastic.co/u/greco)\
**Post date:** [March 8, 2024, 1:44pm UTC](https://discuss.elastic.co/t/elastic-latest-transform-is-not-working-if-sync-time-and-sort-time-is-different/355001/7 "2024-03-08T13:44:19Z")

</div>

Another reason for missing update, as pointed by @przemekwitek[here](https://discuss.elastic.co/t/transform-is-only-partially-updated/351935/10) is the following : when the document is ingested into source index, its timestamp is "old", i.e.: older than `60s` (the configured delay) than the actual server timestamp.

Yet that can be fixed by either :

- using _@timestamp_ field in the `sync.time` property, as you did originally and with a lower frequency setting,
- or, _@timestamp_ is not the ingested time, by setting up an ingest pipeline on the **source** index that will populate a new `event.ingested` field for every source document and then to use `event.ingested` field in the `sync.time` section of the transform config.

---

_[View the full topic](https://discuss.elastic.co/t/elastic-latest-transform-is-not-working-if-sync-time-and-sort-time-is-different/355001)._