Issue with "Continue (using error output)" - never any output

Questions
1

Greeting everyone,
I would really appreciate some pointer or assistance.

I have an issue with “Continue (using error output)” on some nodes (send mail,mssql), i haven’t tried it with all nodes

I did not see any error but no output is emitted if i set “Continue (using error output)” there is no output

Example workflow:
image

Using “Continue”:

image
image1287×740 21.8 KB

Using “Continue (using error output)”:

image
image1263×827 31.8 KB

  • n8n version: 1.62.3
  • hosted PostgreSQL
  • Running N8N via docker compose
  • Operating system Debian bookworm
1 Like
2

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:
3

Not sure how well it’s documented, but it looks specifically for an “error” object. This isn’t always the case as it was introduced after many nodes were built. Another example is Jira which doesn’t work with error output because from memory it uses errorMessage.

4

I am not sure this is the issue.

Even when execution should be successful i get and empty response.

Response for successful execution:

5

Hi! I have the same problem my workflows. After updating from 1.60.1 to 1.62.4, it seems that something has changed in the new releases. Is there a solution? I roll back and get the error “column User.api Key does not exist”

1 Like
6

Also have encountered this error over the weekend (my docker instance updates at the weekend).
Was just writing a question and this popped up which looks the same:

Describe the problem/error/question

When doing a simple mysql select (actually mariaDB server) using a SELECT statement in a mysql node (node v2.1 originally, but now upgraded to 2.4 and acting the same), I get the expected results when the ‘On Error’ option is set to Stop or Continue, but when I set it to ‘Continue (using error output)’ I get neither a result nor an error.
The same happens if I use a ‘Select’ operation instead of ‘Execute SQL’.

What is the error message (if any)?

No error - ‘No output data returned’

Please share your workflow

Obviously this is just one node, but it makes no difference if it’s part of another flow or running standalone. Not much point in including it here, but just in case.

Workaround

I’ve set the node in question to simply continue on error now, but that will cause problems if there’s a genuine error to deal with (fortunately, these are rare).

Information on your n8n setup

Debug info

  • n8nVersion: 1.62.5
  • platform: docker (self-hosted)
  • nodeJsVersion: 20.18.0
  • database: postgres
  • executionMode: regular
7

I ended up rolling back to 1.60.1 and adding the column to DB.
I am using PostgreSQL so I just added the column apiKey as varchar 255 default NULL

8

You could solve it in a way that is longer, less neat, but it will account for errors.
Just use “Continue” and relay the error through the regular output, than add a few “IF” to see if there was an error

9

Thanks Oren,

If that node errors, we have bigger problems to worry about (like the DB server is probably offline). I’m assuming it’s a new bug and will hopefully get fixed pretty quickly, but I’ll have to look through all my workflows and find what’s affected if not.

1 Like
10

Seems to be fixed after my weekly update (now at 1.63.4).

Edit: see also this comment though now mySQL node sorting reversed with use error output

1 Like
11

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