HTTP Node failing but previous worked - no changes have been made

Questions
1

Hi

Describe the problem/error/question

We’re getting a failure in an HTTP node in workflow. This workflow has been operating correctly for months.

What is the error message (if any)?

Item Index

0

Node type

n8n-nodes-base.httpRequest

Node version

4.2 (Latest)

n8n version

1.76.1 (Cloud)

Time

2/11/2025, 2:23:33 AM

Stack trace

NodeApiError: Bad request - please check your parameters at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/HttpRequest/V3/HttpRequestV3.node.js:525:33) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:632:19) at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:890:51 at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:1224:20

Please share your workflow

Share the output returned by the last node

See above.

Information on your n8n setup

instance information

Debug info

core

  • n8nVersion: 1.76.1
  • platform: docker (cloud)
  • nodeJsVersion: 20.18.2
  • database: sqlite
  • executionMode: regular
  • concurrency: 999
  • license: community
  • consumerId: 00000000-0000-0000-0000-000000000000

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 720 hours
  • maxCount: 25000 executions

client

  • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/132.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2025-02-11T14:07:39.993Z

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

Hi !

Usually when a workflow HTTP request stops working out of the blue its due to that third party API. Not saying it’s the case here but worth exploring .

Can you compare the broken execution vs a working one, specifically that node’s input data to check if it’s the same?

Did the credentials change as well or a token expired?

Hope this helps!

4

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