OpenAi Agent : No response. Make sure the last executed node outputs the content to display here

Hi everyone.
I’m executing my flow using the chat trigger with message “hi” to my RAG OpenAi Agent.
my Rag agent is set to “Always output data”

error:
First message always receive the output:
No response. Make sure the last executed node outputs the content to display here.

After that, even the same message, it starts to work properly.
It was working in another cloud account using a different version, so I downloaded my flow and import in a different account and it’s happening now.


Information on your n8n setup

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

Can someone help me, please?

I have the same issue.
In a workflow with several branches, one branch happily outputs the final node’s output, yet in another branch a valid output, formatted

[
  {
    "output": "This is where the acual output text would be"
  }
]

is not displayed in the chat wind, but instead I get the message
[No response. Make sure the last executed node outputs the content to display here]

inspecting the node I can see the output I was expecting in the JSON field ‘output’, yet it will not show up in the chat window.
Confusingly the final node in the other branch produces JSON just like that, whihc is displayed just fine.
I’ve tried mapping the JSON into different formats, I used the field ‘text’ instead of ‘output’, but I always get the [No response…] error.
What am I missing?

Hi there,

usually this error is returned when the output format is off.
Can you share an example of what the agent is actually outputting? Ideally, if you could share a demo workflow with some pinned data, that would help a lot to debug.

Thanks :slight_smile:

I solved my problem by removing the fork part in my flow.
one of the paths returned before the main path and caused the error.

1 Like

Same here!
(Sorry, I should have updated this thread once I had found a solution).
The issue occurred in one particular branch of my workflow where the original chat input had been lost after a few transformations. Picking the original content up from an upstream node fixed it.

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