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 
1 Mi Piace
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 Mi Piace
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.