-
-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error getting embeddings for files #289
Comments
Same issue here on my end as well. |
@ahamedzoha if the test API key fails then something is wrong with your API key or account. 🌴 |
@khoip1311 check the developer console log for errors. If you're getting error code 429, then you probably need to setup billing in your OpenAI API account. |
oh yes, I encounter the same as I test my API keys |
me too |
hi, i'm encountering an Error getting embeddings for: my current note. i'm unsure how to fix the issue. i have only just installed the plug-in and am very much looking forward to using it. Do you have any solutions to this issue? thanks |
I just installed the plugin today. I set up my API key and filled in the appropriate Smart Connections fields. I even put a payment method (and limits!) in at OpenAI, just in case that was the issue. I'm still getting I turned on the log_render and log_render_files options but I don't know where the "console" is to open it. (I turned them on because "log" seemed like a debugging setting...) |
@annekaelber now that it's been some time since adding payment to your OpenAI API account, use the "retry failed files" button and see what happens. Sometimes it takes a few hours before the account rate-limits are increased. If you're still having issues after that, the developer console can be opened using Brian 🌴 |
I want to ask if any people encounter this problem. Many of my files couldn't get embeddings (especially recent ones); It always shows: "Error getting embeddings for:...".
I tried to retry failed files in the settings and make new API keys, but they didn't work.
Any solutions? Thanks!
The text was updated successfully, but these errors were encountered: