Check the Supabase database

Oct 13, 2025 by leolavanderia.com.br 63 views

Troubleshooting n8n Questions of V2 and V3 RAG AI Agent

Introduction

As a user of the n8n RAG AI Agent, you may encounter issues with the V2 and V3 versions of the agent. In this article, we will address two main questions: creating the documents table manually in Supabase for V2 and troubleshooting the slow issue with V3. We will also discuss the best way to clean Supabase and the shared folder.

V2: Creating the Documents Table Manually in Supabase

The documents table is a crucial component of the n8n RAG AI Agent, and it seems that it is missing in your setup. To create the documents table manually in Supabase, you will need to know the column names and types. Here is the information you need:

Column Name	Data Type
id	uuid
name	text
description	text
created_at	timestamp
updated_at	timestamp

You can create the documents table in Supabase using the following SQL query:

CREATE TABLE documents (
  id uuid PRIMARY KEY,
  name text NOT NULL,
  description text,
  created_at timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  updated_at timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP
);

V3: Troubleshooting the Slow Issue

You have encountered a slow issue with the V3 Local Agentic RAG AI Agent, and you are unsure how to troubleshoot it. Here are some steps you can take to identify the issue:

Check the credentials: Ensure that all three items in the Credentials section are set to "connection tested successfully".
Verify the tables: Check that the two tables "document_metadata" and "document_rows" are created in Supabase.
Restart the agent: Try restarting the agent by running the command docker compose down and then python3 start_services.py --profile cpu.
Monitor the output: Check the output of the workflow to see if any errors are occurring.
Check the Supabase database: Verify that the records are being inserted into the Supabase database.

Troubleshooting the Slow Issue: GPU or Wait?

To troubleshoot the slow issue, you may need to use a GPU or wait to see which node is slow. Here are some steps you can take:

Check the system resources: Use the top command to check the system resources and see if any processes are consuming excessive CPU or memory.
Use a GPU: If you have a GPU available, you can try running the agent on it to see if it improves performance.
Wait and observe: Let the agent run for an extended period and observe the output to see if any errors occur.

Cleaning Supabase and the Shared Folder

To clean Supabase and the shared folder, you can follow these steps:

Delete records: Use the Supabase console to delete any records that are no longer needed.
Drop tables: Use the Supabase console to drop any tables that are no longer needed.
Clear the shared folder: Use the rm command to delete any files in the shared folder that are no longer needed.

Conclusion

In conclusion, troubleshooting the n8n RAG AI Agent can be a complex process, but by following these steps, you can identify and resolve issues with the V2 and V3 versions of the agent. Remember to create the documents table manually in Supabase for V2 and to troubleshoot the slow issue with V3 by checking the credentials, verifying the tables, restarting the agent, monitoring the output, and checking the Supabase database. Additionally, cleaning Supabase and the shared folder can help resolve issues caused by incorrect setup or usage.

Additional Resources

n8n RAG AI Agent documentation
Supabase documentation
Docker documentation
n8n RAG AI Agent V2 and V3 Troubleshooting Q&A

Introduction

As a user of the n8n RAG AI Agent, you may encounter issues with the V2 and V3 versions of the agent. In this article, we will provide a Q&A section to address common questions and issues related to the n8n RAG AI Agent.

Q: What is the documents table, and why is it missing in my setup?

A: The documents table is a crucial component of the n8n RAG AI Agent, and it is used to store metadata about the documents being processed. If the documents table is missing in your setup, you can create it manually in Supabase using the SQL query provided in the previous section.

Q: How do I troubleshoot the slow issue with the V3 Local Agentic RAG AI Agent?

A: To troubleshoot the slow issue with the V3 Local Agentic RAG AI Agent, you can follow these steps:

Check the credentials to ensure that all three items are set to "connection tested successfully".
Verify that the two tables "document_metadata" and "document_rows" are created in Supabase.
Restart the agent by running the command docker compose down and then python3 start_services.py --profile cpu.
Monitor the output of the workflow to see if any errors are occurring.
Check the Supabase database to verify that the records are being inserted.

Q: Do I need to use a GPU to troubleshoot the slow issue?

A: Using a GPU may help improve performance, but it is not a requirement to troubleshoot the slow issue. You can try running the agent on a GPU to see if it improves performance, but it is not a necessary step.

Q: How do I clean Supabase and the shared folder?

A: To clean Supabase and the shared folder, you can follow these steps:

Delete any records that are no longer needed using the Supabase console.
Drop any tables that are no longer needed using the Supabase console.
Clear the shared folder by deleting any files that are no longer needed using the rm command.

Q: What are some common issues that can cause the slow issue?

A: Some common issues that can cause the slow issue include:

Incorrect setup or configuration of the n8n RAG AI Agent.
Insufficient system resources (e.g. CPU, memory, disk space).
Network connectivity issues.
Supabase database issues.

Q: How can I prevent the slow issue from occurring in the future?

A: To prevent the slow issue from occurring in the future, you can follow these best practices:

Ensure that the n8n RAG AI Agent is properly configured and set up.
Monitor system resources and adjust as needed.
Regularly clean Supabase and the shared folder.
Use a GPU to improve performance (if available).

Q: Where can I find additional resources for troubleshooting the n8n RAG AI Agent?

A: You can find additional resources for troubleshooting the n8n RAG AI Agent in the following locations:

n8n RAG AI Agent documentation: https://n8n.io/docs/introduction/rag-ai-agent/
Supabase documentation: https://supabase.io/docs
Docker documentation: https://docs.docker.com/

Conclusion

In conclusion, troubleshooting the n8n RAG AI Agent can be a complex process, but by following these steps and best practices, you can identify and resolve issues with the V2 and V3 versions of the agent. Remember to create the documents table manually in Supabase for V2 and to troubleshoot the slow issue with V3 by checking the credentials, verifying the tables, restarting the agent, monitoring the output, and checking the Supabase database. Additionally, cleaning Supabase and the shared folder can help resolve issues caused by incorrect setup or usage.