Catching MSSQL Query Execution Error

Questions
1

When executing a workflow that contains a Microsoft SQL Server ‘Execute Query’ function, the only exit option for catching an error response is to stop the workflow. This does not allow for building API endpoints that can return any status error codes.

When executing the query, if you select the ‘on error’ function, ‘stop workflow’ will show the error. If you select ‘continue’ or ‘continue using error output’ the workflow simply continues to pass the previous nodes values and does not show any SQL error messages.

Hopefully I have provided enough information for some ideas or assistance. I can’t really share the flow as it contains all our SQL Server information.

Information on your n8n setup

n8n version 1.20.0 **
Running n8n via npm **
Operating system: Ubuntu Server **

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

Hi @Syfan_IT :wave: Had a test of this and this does indeed look to be a bug - I’ll let our engineers know that you encountered this, and be back with any updates when I have them!

6

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