-
Notifications
You must be signed in to change notification settings - Fork 3k
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: Failed to ingest your data #108
Comments
I had exactly the same problem last night. It was related to OpenAI api. My api expired and I ended up adding a CC to my account then it worked again. |
it will help to solve this issue from this link |
Hi, @josh-may! I'm Dosu, and I'm helping the gpt4-pdf-chatbot-langchain team manage their backlog. I wanted to let you know that we are marking the issue titled "Error: Failed to ingest your data" as stale. Based on my understanding, you were experiencing an error while trying to ingest data. You mentioned that you checked your API key and environment, and everything seems to be correct. Another user suggested checking the PINECONE_INDEX_NAME and adding the "short" name. Additionally, another user mentioned that their issue was resolved by adding a credit card to their OpenAI API account. A link was also shared to help solve the issue. Before we close this issue, we wanted to check with you if it is still relevant to the latest version of the gpt4-pdf-chatbot-langchain repository. If it is, please let us know by commenting on the issue. Otherwise, feel free to close the issue yourself, or it will be automatically closed in 7 days. Thank you for your understanding and contribution to the gpt4-pdf-chatbot-langchain repository! |
I am having the same issue, what shall I do ? |
Anyone else experience this? I tried with the PDFs included in the repo as well as others. Below is the error - "request failed and the interceptors did not return an alternative response".
Screen.Recording.2023-04-02.at.6.45.46.AM.mov
I added a console log inside ingest-data.ts. Which shows my api key and environment. And everything looks good.
The text was updated successfully, but these errors were encountered: