The issue with the OpenAI’s embeddings config was resolved here:
There’s a migration there that will copy the data and set the selected model setting for you unless you have already configured it manually.
Additionally, I merged this change which will help mitigate the impact of the feature being in a broken state due to config:
I hear what you said about the configuration being overwhelming. We’ve been working on improving the UX by moving how LLMs are configured, and now we have done the same with embeddings, which led to the removal of +25 site settings. These changes often require us to rewrite a big part of the plugin internals though, so they take time and effort but you can expect things to keep improving over time.
Regarding the restoration issues you mentioned, it’s unclear to me if this is a recurrent issue with the backup not capturing the tables where AI models config live. If so, let me know and I’ll investigate.
For this particular case, the problem was a bug in the database migration I wrote, which grabs data from multiple site settings and inserts a row in the embeddings config table. The bug turned it into a no-op for Open AI models and it’s unrelated to backup/restores.