# Request for a date picker in AI Translate settings

**URL:** https://meta.discourse.org/t/request-for-a-date-picker-in-ai-translate-settings/405828
**Category:** Feature
**Tags:** completed, ai, dynaloc, content-localization
**Created:** [June 22, 2026, 3:13pm UTC](https://meta.discourse.org/t/request-for-a-date-picker-in-ai-translate-settings/405828 "2026-06-22T15:13:36Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![LotusJeff](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lotusjeff/32/477888_2.png) [@LotusJeff](https://meta.discourse.org/u/LotusJeff)
#### Post date: [June 27, 2026, 4:15pm UTC](https://meta.discourse.org/t/request-for-a-date-picker-in-ai-translate-settings/405828/4 "2026-06-27T16:15:17Z")

</div>

I was reviewing the translation data last night and found another reason why a **date picker** would be beneficial.

The translation process appears to translate **topics** much faster than **posts**. Without a specific cutoff date, you can end up with translated topics whose underlying posts have not yet been translated.

For example, I have my Discourse instance configured with a **365-day backfill**. As of this morning:

- **Topics** have been translated back to **June 25, 2025**.
- **Posts** have only been translated back to **May 17, 2025**.

Based on the current rate, I estimate it will take approximately **50 more days** (around **August 15** ) for the post translations to catch up.

This means there will be a significant period where users can browse translated topics, only to find portions of the discussion still untranslated.

My assumption is that adding a **date picker** (translate content after a specified date) would be a much simpler solution than changing the translation logic to ensure every post within a translated topic has also been translated.

---

_[View the full topic](https://meta.discourse.org/t/request-for-a-date-picker-in-ai-translate-settings/405828)._