Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix TypeError: Invalid URL in appendResumeToken after update to v2.17.8+ from v2.13.4 [1 comments, 2 participants]

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…
GitHub stats
n8n-io/n8n#29533•Fetched 2026-04-30 06:43:58
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
YazyNYazyN
Participants
n8n-assistant[bot]n8n-assistant[bot]YazyNYazyN
Timeline (top)
commented ×1labeled ×1mentioned ×1subscribed ×1

Error Message

After updating n8n from 2.13.4 to 2.17.8+, all workflows utilizing Set, Postgres, or HTTP nodes fail with a TypeError: Invalid URL occurring in the appendResumeToken function. This error does not occur in 2.13.4 using the same environment configuration. I didn't try with lower versions but i expect the same behaviour.

  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

After updating n8n from 2.13.4 to 2.17.8+, all workflows utilizing Set, Postgres, or HTTP nodes fail with a TypeError: Invalid URL occurring in the appendResumeToken function. This error does not occur in 2.13.4 using the same environment configuration. I didn't try with lower versions but i expect the same behaviour.

To Reproduce

  1. Deploy n8n 2.17.8 (or higher) with standard Postgres/HTTP node configurations.
  2. Trigger a workflow containing a Set, Postgres, or HTTP node.
  3. Observe execution failure immediately.

Expected behavior

The workflow should execute successfully as it did in version 2.13.4, with nodes correctly resolving internal state and callback URLs without triggering a TypeError during the appendResumeToken process.

Debug Info

Debug info

core

  • n8nVersion: 2.13.4
  • platform: docker (self-hosted)
  • nodeJsVersion: 24.13.1
  • nodeEnv: production
  • database: postgres
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)
  • consumerId: c00c542f-edc1-4b60-a45a-4683021d4282

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/145.0.0.0 safari/537.36 opr/129.0.0.0
  • isTouchDevice: false

Generated at: 2026-04-29T15:21:01.814Z

Operating System

Ubuntu Linux

n8n Version

2.13.4

Node.js Version

24.13.1

Database

PostgreSQL

Execution mode

main (default)

Hosting

self hosted

extent analysis

TL;DR

Downgrade n8n to version 2.13.4 to potentially resolve the TypeError: Invalid URL issue occurring in the appendResumeToken function.

Guidance

  • Verify that the error is indeed caused by the version update by testing with a lower version of n8n.
  • Check the configuration of the Set, Postgres, and HTTP nodes to ensure they are correctly set up and compatible with the updated version of n8n.
  • Review the release notes for n8n versions 2.14.0 to 2.17.8 to see if there are any known issues or changes that could be causing the error.
  • Test the workflow with a minimal configuration to isolate the issue and determine if it's specific to certain nodes or settings.

Notes

The provided debug information is for n8n version 2.13.4, which is not the version that's experiencing the issue, so it may not be directly relevant to the problem.

Recommendation

Apply workaround: Downgrade to version 2.13.4, as it is known to work with the current configuration and the issue seems to be introduced in a later version.

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

The workflow should execute successfully as it did in version 2.13.4, with nodes correctly resolving internal state and callback URLs without triggering a TypeError during the appendResumeToken process.

#GPU setup#container setup#orchestration issue#cache issue#memory leak

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 TypeError: Invalid URL in appendResumeToken after update to v2.17.8+ from v2.13.4 [1 comments, 2 participants]