# Anomoly detection jobs. latest timestamp is updating but more than 2 months back

**URL:** <https://discuss.elastic.co/t/anomoly-detection-jobs-latest-timestamp-is-updating-but-more-than-2-months-back/385311>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-machine-learning\
**Created:** [March 3, 2026, 8:23am UTC](https://discuss.elastic.co/t/anomoly-detection-jobs-latest-timestamp-is-updating-but-more-than-2-months-back/385311 "2026-03-03T08:23:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Whoami1980](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/whoami1980/32/147545_2.png) [@Whoami1980](https://discuss.elastic.co/u/Whoami1980)\
**Post date:** [March 3, 2026, 8:23am UTC](https://discuss.elastic.co/t/anomoly-detection-jobs-latest-timestamp-is-updating-but-more-than-2-months-back/385311/1 "2026-03-03T08:23:07Z")

</div>

Being a newbie to ML.  
Can anyone advice where I should start troubleshooting?

job-name:noise-reduction-system-metrics-consolidated  
job state: opened. memory status: ok.  
latest timestamp is updating but more than 2 months back

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![richcollier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/richcollier/32/115035_2.png) [@richcollier](https://discuss.elastic.co/u/richcollier)\
**Post date:** [March 3, 2026, 7:24pm UTC](https://discuss.elastic.co/t/anomoly-detection-jobs-latest-timestamp-is-updating-but-more-than-2-months-back/385311/2 "2026-03-03T19:24:48Z")

</div>

screenshot of the jobs screen? Is that job actually running?

---

<div class="post-metadata">

**Author:** ![Whoami1980](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/whoami1980/32/147545_2.png) [@Whoami1980](https://discuss.elastic.co/u/Whoami1980)\
**Post date:** [March 4, 2026, 9:13am UTC](https://discuss.elastic.co/t/anomoly-detection-jobs-latest-timestamp-is-updating-but-more-than-2-months-back/385311/3 "2026-03-04T09:13:53Z")

</div>

@richcollier The job is definitely running. Its the only job which appears to have a very large, processed record. Is there anything i can zoom into?

---

<div class="post-metadata">

**Author:** ![richcollier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/richcollier/32/115035_2.png) [@richcollier](https://discuss.elastic.co/u/richcollier)\
**Post date:** [March 4, 2026, 5:15pm UTC](https://discuss.elastic.co/t/anomoly-detection-jobs-latest-timestamp-is-updating-but-more-than-2-months-back/385311/4 "2026-03-04T17:15:09Z")

</div>

My apologies, I misread your original post. You said the latest timestamp _is_ updating. I read that as _is not_.

Ok, so if it is updating but is more than 2 months back, that means that you asked the job to analyze a lot of historical data and it is attempting to do that. However, it appears to be taking a long time to go through that historical data either because a) it is a massive amount of data, and/or b) your cluster cannot manage what’s being asked of it.

You really need to determine if the pace at which the job is progressing in the effort of looking this far back over time is faster than “real-time”. In other words, watch the progression and assess the speed at which it will catch up to “now” (if it ever will).

You could consider not having the job look back in time, but rather just process real-time data and just wait a few weeks. You could also consider refactoring the ML job to make it more efficient