This is really minor one, more level beauty glitch. But this is in use, and translations are working.
But it gave me small and short incident of arrhythmia 
2 לייקים
Sorry, not following, what is wrong here?
Translations were, and is, enabled. Not disabled, as that screen tells.
Odd, @nat is working on this screen it should be showing progress.
The feature is deemed enabled if
discourse_ai_enabled
ai_translation_enabledcontent_localization_supported_localeshas valuesai_translation_backfill_max_age_daysis more than 0ai_translation_backfill_hourly_rateis more than 0
@Jagster Can you share these values and the state of your graph?
That said, perhaps we can reduce the requirements to show this graph, but the graph would be empty if the first four is not satisfied.
Well, then it could be some glitch in the Matrix. I do upgrades quite often, so it can be fixed, even there is no obvious reason.
Maybe the text should say something like “Automatic backfill of translations is disabled, click below to configure” if only these two settings prevent the graph from showing.
Then no one has to worry that translations are disabled in general
לייק 1
My content is translated, and on that side isn’t any issue contentwise.
But:
- supported locales are fi, sv, et, en_US and de. Default is fi, done in web_only.yml
- backfill-max_age is 365
- backfill_hourly_rate is 15
The graph is specific to the AI features, and only made to show up when all of the five settings are set accordingly. So @Jagster there is some incomplete information here above …
One thing I can remove from the requirement is the backfill_hourly_rate, but other than that I don’t think it could work.
Sorry, my bad. I thought those enabled points are obvious.
Both, ai and translation, are enabled.
I see. And just to double-confirm, right now with all the five above satisfied, you are still seeing it disabled per OP?
Yes, still.
I can do rebuild and try if that puts things in the order. Because if I’m the only one, then the issue must be on my side.
I think that would be good. There has been new chart updates today.
An additional thing to check is if each of your personas for translations have a valid LLM configured. (In case you are curious, this whole file does the validation)
2 לייקים
No luck. I changed default locale from fi to en_US by commenting DISCOURSE_DEFAULT_LOCALE: fi and changing it from settings, and that didn’t help either. Safe mode gave same.
I have this in web_only.yml and data.yml:
LANG: fi_FI.UTF-8
LANGUAGE: fi_FI.UTF-8
I tried to change those to en_US.UTF-i in both ymls, but that crashed rebuilds.
Anyway — I would say it isn’t matter of locales either 
Ill start digging personas, but those should be default ones, I havent edited any of those.
After all — this isn’t bigger issue.
Ok, you had good hunch.
discourse(prod)> SiteSetting.ai_translation_backfill_hourly_rate
=> 0
When I changed this to 15 (well, anything over zero would work, of course) I got charts.
The big question is why it was zero? Why didn’t it follow setting AI summary backfill maximum topics per hour?
edit those two aren’t same setting?
Hmm no they are different features altogether and should appear in the respective feature settings.
Have a look at Summarize - Gists.
לייק 1
Next stupid question:
When SiteSetting.ai_translation_backfill_hourly_rate => 0 why I got translations after all? I’m close to 100% with translations. And why is it still a hidden setting?
Don’t worry about the questions, they’re not stupid and in fact they help us figure out gaps with our product. 
The backfill is for communities who would like very old topics to be translated. All new posts and topics are translated when created or edited.
The progress chart is important for old communities like Discourse that have a lot of history that needs translating at a controlled pace.
It’s a hidden setting and default to 0 for now due to a few reasons, one of them being that this feature can be wildly misconfigured – a site may have many old posts, and the site owner may choose up to 10 or more languages. This would incur a large bill. Besides that, if the chosen LLM is the same one for other features like spam detection, getting rate limited would be not ideal.
לייק 1
I kind of understand that, but I thought SiteSetting.ai_translation_backfill_max_age_days is there to limit amount of history, and SiteSetting.ai_translation_backfill_hourly_rate is just slowing down things, right? If so, then why I got backfill, even that hidden setting was zero? That is what I don’t get now.
That is right.
Backfill hourly rate affects older posts defined in max age days, they work hand-in-hand. It should not translate posts that are old if the value is zero. All these are run in backfilling jobs (hence the backfill in the setting names).
Are you seeing old posts getting translated even with ai_translation_backfill_hourly_rate set to 0?