Aamir
Aamir2mo ago

The RAG system was working well before, but now I'm encountering errors:

Hi Team, The RAG system was working well before, but now I'm encountering errors: "buffer is not an object" and "pdf to text is not a string." The same workflow was running successfully without any error previously. I've attached a Loom video for reference, and I've noticed that others are experiencing this issue as well. Please check and rectify this as soon as possible. Thank you, https://www.loom.com/share/d9745c5a79ed43c3bc01e875a7f70e3c?sid=548e51d5-5751-448f-adf9-2267a27c5c26
5 Replies
AI Support
AI Support2mo ago
AI Support Bot Information
<@1343468444515041280> you can react on the relevant answer (message) with a ✅ in this thread when you think it has been solved, by the bot or by a human! Anyone can react on this message with a ❌ if the GPT bot is unhelpful or hallucinating answers. Please note: Team members will review and answer the questions on best efforts basis.
AI Support
AI Support2mo ago
AI Response
It seems that there isn't an exact match in the FAQ section regarding the error "buffer is not an object" and "pdf to text is not a string." Given that these errors were not present previously and others are experiencing this same issue, it may be advisable to file a support request directly through the BuildShip app. This would allow the technical support team to investigate the issue more thoroughly and provide a timely solution. Please consider using in-app support for further assistance.
BuildShip AI Support
Gaurav Chadha
Gaurav Chadha2mo ago
Hey @Aamir The RAG template is updated, could you clone again and test? I think @Luis from our team has already sent you an email regarding this.
Cemre Sancaktar
Hey, I had the exact same problem Amir had. I create a new wf from the template. When I make a request I get an error. Can you help me troubleshoot this issue?
No description
Luis
Luis5w ago
Hi @Cemre Sancaktar, can you share more info on the error you're getting on the Generate Embeddings node or submit an in-app request. We did push an update that fixes the validation errors mentioned in the original issue above.

Did you find this page helpful?