I’m trying to enable automatic content localization (AI translation backfill) on my self-hosted Discourse instance and I’ve followed all the available guidelines, but I’m not seeing any translations appear. Here’s what I’ve done so far: Enabled content localization enabled Selected at least one l…

[Bild] nat: As mentioned by @GrahamM ai_translation_backfill_hourly_rate needs to be set by your site admin as it is a hidden setting. We’ve most recently unhidden the setting ai_translation_backfill_hourly_rate in this PR . That setting defaults to 0, and was originally hidden so that only h…

Yes I saw that and changed it from 0 to 10 (see the screenshots above) and it’s still saying that backfill is disabled with no scheduled jobs. Is there some way to kick start it or is something else required? I’ve tried a 100 also but still no joy.

What posts are you trying to translate? Bot posts (users with ids <= 0) are not sent for translations. Are your posts in private categories?

The whole site in general, want to use users options to see posts in different languages. Not bot or private, 1000’s of public posts. Now this is very weird, when I see the dashboard now (19 hours later), I see this. It’s saying backfill is disabled but seems to have started doing some posts but it…

Huge thanks to @nat for looking into this, for others reference, the ai_translation_backfill_hourly_rate is different from ai_summary_backfill_hourly_rate and I was mixing them up. @nat it looks like the Translations backfill is now enabled, I see this in the dashboard Translation Progress Back…

Can you set the value to 20 please? The translate job runs every 5 minutes, meaning the job will run 12 times an hour. There is some integer division going on here making the rate 0 when you take 10 ÷ 12 to get the limit per run.

Done will keep an eye on it, assuming this integer rounding issue will be handled in future. Does the same issue also impact AI summary backfill maximum topics per hour? EDIT: I can’t use 20 per hour with the current model (along with other AI featuers), it’s overflowing the model rate limits. Can…

20 per hour would mean approx only 1 every 5 minutes. This will definitely not hit rate limits.

Oddly it seems to be hitting the limits. Before starting translations backfill, using discourse AI search/helper bot would work fine (which was the primary use of AI). But now it’s hitting the Gemini Flash 2.5 limits which is is 10 RPM, 250,000 TPM and 250 RPD. From the logs it appears that it’s hit…

I don’t recommend using the free tier for translations. Translating a simple post can wipe out all the quota in the free tier. You can use the following query to check which post is using up the tokens: -- [params] -- date :start_date = '2025-11-01' SELECT feature_name, created_at, post_id…

KI-Übersetzungs-Backfill funktioniert nach Konfiguration aller Einstellungen nicht mehr

Unterstützung

Falco (Falco) 12. November 2025 um 03:26 36

Wir haben den bezahlten Google Gemini-Tarif erfolgreich genutzt, um in den letzten Wochen mehr als eine Million Beiträge hier auf Meta zu übersetzen, daher kann ich bestätigen, dass es problemlos funktioniert.

Thema		Antworten	Aufrufe
How to configure ai translate of `Ai translation backfill hourly rate`? Support ai	9	307	4. November 2025
AI setting tells translations are disabled when enabled Bug ai , content-localization	21	431	1. September 2025
Content Localization - Manual and Automatic with Discourse AI Site Management ai , content-localization	53	4299	10. Februar 2026
The usage problem after using AI translation Support ai , dynaloc	7	307	15. Juli 2025
Discourse Translator Plugin official , multi-lingual , translator	29	71431	24. Juni 2026

KI-Übersetzungs-Backfill funktioniert nach Konfiguration aller Einstellungen nicht mehr

Verwandte Themen