N8n node returns 400 error after upgrading to 1.2.1

After upgrading to 1.2.1 it seems the n8n node no longer works. It just returns 400 errors when:

  • Get Execution
  • Get Many Executions
  • Get Workflow
  • Get Many Workflows

Other facts:

  • The API playground with same API key still works fine
  • The node can fetch/pre-populate the list of workflows still

What is the error message (if any)?

ERROR: Request failed with status code 400
10/08/2023, 9:56:23 pm

NodeApiError: Request failed with status code 400
    at RoutingNode.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/RoutingNode.js:114:23)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:686:23)
    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:631:53

Please share your workflow

Information on your n8n setup

  • n8n version: 1.2.1
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu (host)
1 Like

Hey @pemontto,

It looks like this is fixed in the latest master branch so should hopefully be resolved in the next release.

1 Like

Hi. Same issue here after upgrade to 1.2.1 problem being that your test workflow for datetime checkup uses that module.
Any solution apart from waiting for next release? Can we use another 1 version?

Hey @luison,

1.1 is ok to use and we should be doing another release soon which should resolve this.

1 Like

1.1.1 worked, thanks.
I am assuming no output from the last command (Find params with affected expressions) on the workflow means none affected by the change.

Thanks again.

Hey @luison,

I believe that should be the case. The good news is 1.2.2 has been released which fixes this issue.


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