# Incorrect Timestamp in Machine Learning Job Result

**URL:** <https://discuss.elastic.co/t/incorrect-timestamp-in-machine-learning-job-result/99111>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-machine-learning\
**Created:** [September 1, 2017, 10:12am UTC](https://discuss.elastic.co/t/incorrect-timestamp-in-machine-learning-job-result/99111 "2017-09-01T10:12:44Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![droberts195](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/droberts195/32/17692_2.png) [@droberts195](https://discuss.elastic.co/u/droberts195)\
**Post date:** [September 7, 2017, 9:05am UTC](https://discuss.elastic.co/t/incorrect-timestamp-in-machine-learning-job-result/99111/6 "2017-09-07T09:05:55Z")

</div>

Is it possible that the data you are analyzing contains timestamps in text format in the India timezone but without the timezone in the textual representation? In this case you'll end up with a `_source` document that shows your original textual representation, which you'll interpret as India time. But Elasticsearch will have converted it to epoch milliseconds to store in the doc values on the assumption it's UTC. Then ML will analyze it and create results based on the epoch milliseconds stored in the doc values.

This thread discusses the way Elasticsearch converts textual timestamps assuming UTC unless the text contains a timezone: [Storing Dates in Elastic Best Practices](https://discuss.elastic.co/t/storing-dates-in-elastic-best-practices/57496/2)

If what I'm suggesting isn't clear then it might be easier to discuss a specific example. If you paste the `_source` of one of the documents you're analyzing then I can talk specifically about it.

---

_[View the full topic](https://discuss.elastic.co/t/incorrect-timestamp-in-machine-learning-job-result/99111)._