Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix RSS Feed Trigger ignores "Continue (using error output)" on HTTP 404/500 and triggers Error Workflow instead

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

On Error: Continue (using error output) HTTP errors returned by the feed endpoint (such as 404 Not Found and 500 Internal Server Error) do not follow the configured error handling behavior. Instead of routing the execution through the node's error output, the workflow execution fails and triggers the configured Error Workflow. This behavior appears inconsistent with the expected semantics of "Continue (using error output)", where recoverable node errors should be emitted through the error output path. 4. Set On Error to Continue (using error output). 5. Connect the node's error output to another node for error handling.

  • The node should honor the configured Continue (using error output) setting.
  • The error should be emitted through the node's error output.
  • The workflow should continue through the error branch.
  • The global Error Workflow should not be triggered for handled node errors.
  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

When using an RSS Feed Trigger configured with:

Retry on Fail: Enabled On Error: Continue (using error output)

HTTP errors returned by the feed endpoint (such as 404 Not Found and 500 Internal Server Error) do not follow the configured error handling behavior.

Instead of routing the execution through the node's error output, the workflow execution fails and triggers the configured Error Workflow.

This behavior appears inconsistent with the expected semantics of "Continue (using error output)", where recoverable node errors should be emitted through the error output path.

To Reproduce

  1. Create a workflow containing an RSS Feed Trigger.
  2. Configure the RSS Feed Trigger to use a feed URL that returns HTTP 404 or HTTP 500.
  3. Enable Retry on Fail.
  4. Set On Error to Continue (using error output).
  5. Connect the node's error output to another node for error handling.
  6. Activate the workflow.
  7. Wait for the trigger to execute.

Expected behavior

When the RSS Feed Trigger receives an HTTP 404 or HTTP 500 response:

  • The node should honor the configured Continue (using error output) setting.
  • The error should be emitted through the node's error output.
  • The workflow should continue through the error branch.
  • The global Error Workflow should not be triggered for handled node errors.

Debug Info

Debug info

core

  • n8nVersion: 2.22.5
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.15.0
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: 49fa038a-40d9-4463-bf8d-b5d903d5bb00

storage

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

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

client

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

cluster

  • instanceCount: 1
  • versions: 2.22.5
  • instances:
    • instanceKey: eadafc7e-c8e4-4115-8b7f-79761abd955b, hostId: main-cc7239eaae60, instanceType: main, instanceRole: leader, version: 2.22.5
  • checks:
    • check: hostid-clash, status: succeeded, warnings: -
    • check: lifecycle, status: succeeded, warnings: -
    • check: split-brain, status: succeeded, warnings: -
    • check: version-mismatch, status: succeeded, warnings: -

Generated at: 2026-05-29T12:02:13.036Z

Operating System

Ubuntu 24.01

n8n Version

2.22.5

Node.js Version

24.15.0

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

When the RSS Feed Trigger receives an HTTP 404 or HTTP 500 response:

  • The node should honor the configured Continue (using error output) setting.
  • The error should be emitted through the node's error output.
  • The workflow should continue through the error branch.
  • The global Error Workflow should not be triggered for handled node errors.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix RSS Feed Trigger ignores "Continue (using error output)" on HTTP 404/500 and triggers Error Workflow instead