# Transform is only partially updated **URL:** \ **Category:** Elasticsearch\ **Tags:** transforms\ **Created:** [January 28, 2024, 9:30am UTC](https://discuss.elastic.co/t/transform-is-only-partially-updated/351935 "2024-01-28T09:30:13Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![przemekwitek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/przemekwitek/32/79526_2.png) [@przemekwitek](https://discuss.elastic.co/u/przemekwitek)\ **Post date:** [January 30, 2024, 2:39pm UTC](https://discuss.elastic.co/t/transform-is-only-partially-updated/351935/10 "2024-01-30T14:39:24Z")
One more reason for missing updates I can think of is that 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. Usually the solution for that is to have an ingest pipeline on the **source** index that will populate `event.ingested` field for every source document and then to use `event.ingested` field in the `sync.time` section of the transform config. You can find the pipeline code here: > **[How transform checkpoints work | Elasticsearch Guide \[8.12\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/transform-checkpoints.html#sync-field-ingest-timestamp)** --- _[View the full topic](https://discuss.elastic.co/t/transform-is-only-partially-updated/351935)._