N8n-ai cloud - Xata Memory Error

Alex_Stewart · January 8, 2024, 11:25am

Describe the problem/error/question

I am trying to use the Xata platform as a memory server via n8n cloud, using a simple workflow consisting of manual chat → conversation agent with OpenAI node as the model and Xata connected (with the correct credentials) as a memory source. However, the agent returns an error upon execution. Looking at the agent logs, it is replying to me, however it seems it can’t store (or retrieve) the chat session.

What is the error message (if any)?

Error: input values have 2 keys, you must specify an input key or pass only 1 key as input
    at getInputValue (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/@[email protected]/node_modules/@langchain/core/dist/memory.cjs:31:15)
    at Proxy.saveContext (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@google-ai+gen_l2pdhycmx5ubucgl6yjsjdwoyq/node_modules/langchain/dist/memory/chat_memory.cjs:52:75)
    at AgentExecutor.call (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@google-ai+gen_l2pdhycmx5ubucgl6yjsjdwoyq/node_modules/langchain/dist/chains/base.cjs:136:31)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.conversationalAgentExecute (/usr/local/lib/node_modules/n8n/packages/@n8n/nodes-langchain/dist/nodes/agents/Agent/agents/ConversationalAgent/execute.js:57:24)
    at Workflow.runNode (/usr/local/lib/node_modules/n8n/packages/workflow/dist/Workflow.js:696:19)
    at /usr/local/lib/node_modules/n8n/packages/core/dist/WorkflowExecute.js:656:53

Please share your workflow

Share the output returned by the last node

ERROR: input values have 2 keys, you must specify an input key or pass only 1 key as input

Information on your n8n setup

n8n version: n8n@ai-beta
Database (default: SQLite): Xata
n8n EXECUTIONS_PROCESS setting (default: own, main): default
Running n8n via (Docker, npm, n8n cloud, desktop app): Cloud
Operating system: MacOS Sonoma

n8n · January 8, 2024, 11:25am

It looks like your topic is missing some important information. Could you provide the following if applicable.

n8n version:
Database (default: SQLite):
n8n EXECUTIONS_PROCESS setting (default: own, main):
Running n8n via (Docker, npm, n8n cloud, desktop app):
Operating system:

Jon · January 8, 2024, 4:13pm

Hey @Alex_Stewart,

Thanks for the report, I have managed to reproduce this and have created a dev ticket to look into it further which we will be tracking as NODE-1040

Alex_Stewart · January 9, 2024, 4:36pm

Thank you - is there a way for us to see the status of the ticket?

Jon · January 9, 2024, 4:48pm

Hey @Alex_Stewart,

Not at the moment, But maybe we should sort something out for that

Alex_Stewart · January 9, 2024, 5:10pm

Would be great for cases where multiple people report a problem so they can see progress without filling up the forum with questions/replies

Jon · January 10, 2024, 4:11pm

Yeah, I was thinking that. I have found that the search is not used much as well so we may implement some tweaks for that.

Alex_Stewart · January 18, 2024, 8:43am

Any update on this?

Jon · January 19, 2024, 9:32am

Hey @Alex_Stewart,

Not yet, I will take a look at it later today though and see if I can get it sorted in the next release.

Max.M · February 16, 2024, 8:30am

Jon, any update you have on this?

Jon · February 20, 2024, 4:51pm

Hey @Max.M,

I didn’t get a chance to take a look, It should be picked up soon though.

JOduMonT · April 27, 2024, 9:35am

@Alex_Stewart

I reproduced your workflow in my n8n
and it work well for me

my n8n Version is: 1.38.2

Lester_Reynolds · July 10, 2024, 11:50pm

Same problem here. sometimes there is an error, specifically when there is no history to retrieve

Lester_Reynolds · August 10, 2024, 5:59pm

I still have the problem. I tried with Redis memory also, and I am getting the same issue. It looks to me like its a Agent node problem

Lester_Reynolds · August 16, 2024, 3:29pm

still having the problem, with many nodes. No error details.

ria · August 30, 2024, 7:51am

Hi @Lester_Reynolds

Could you try to update to our recent version and see if the error persist? I know we had a bug with the Tool Agent, that got fixed after 1.54

If you keep getting the error, please share your workflow with some pinned dummy data so we can reproduce it.

Thanks!

system · November 28, 2024, 7:51am

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.