AI Agent Error at Postgres Memory node

[LD012025]

System details:

M1 apple 8gb, Sequioa 15.0

Docker version 27.4.0, build bde2b89

Self hosted n8n Version: 1.76.2

Issue:

I test every node up until AI agent and im able to return session id as an output field; however, i get the following error trying to test my workflow:

Docker logs:

2025-03-03 11:48:59 Got unexpected type: undefined

2025-03-03 11:49:00 Got unexpected type: undefined

2025-03-03 11:49:01 Got unexpected type: undefined

n8n output:

Error details

n8n version 1.76.2 (Self Hosted) Time 3/3/2025, 11:49:01 AMError cause {}

[AhmedAlnaqa]

follow the steps here

Step by Step: RAG AI Agents Got Even Better

If my answer rings any bell 🔔 take a step, love it ❤️ and let me know! But if it's correct 👍, please mark it as the accepted solution! Thanks a lot! 😊

Let me know if you’d like any further tweaks!

[LD012025]

I had the same setup but I went ahead and remade my workflow, but the error persists. I also have the right response from the vector store; however, I get the empty output to the user

[LD012025]

I see the right response being sent to my Postgres chat memory, it just never gets back to the user

[AhmedAlnaqa]

plz share ur workflow
to check it

[brauliodiasribeiro]

I have this same error and it started after I added the variables to the stack:

• N8N_RUNNERS_ENABLED=true
• N8N_RUNNERS_MODE=internal
• OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS=true

[AhmedAlnaqa]

@brauliodiasribeiro

8N_RUNNERS_M

Change “.item” to “.first” or “.last”

If my answer rings any bell take a step, love it and let me know! But if it’s correct , please mark it as the accepted solution! Thanks a lot!

Let me know if you’d like any further tweaks!

[LD012025]

@AhmedAlnaqa any insight. on this? I dont have those variables on my stack. i pass session id like this: {{ $json.sessionId }}

[brauliodiasribeiro]

I had already tried, it doesn’t work.
It gives the same error

[brauliodiasribeiro]

The same error in another workflow

[brauliodiasribeiro]

@LD012025 @AhmedAlnaqa

I found the problem.
It was an error in the memory table.
I deleted the table and let it create a new one and it worked.

[LD012025]

[AhmedAlnaqa]

Good to here