Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix Node duplication truncates name when it ends with a decimal-like string (e.g. "Claude Sonnet 4.6" → "Claude Sonnet 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#29152•Fetched 2026-04-28 06:49:36
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
krustev03krustev03
Participants
krustev03krustev03n8n-assistant[bot]n8n-assistant[bot]
Timeline (top)
labeled ×3commented ×1mentioned ×1subscribed ×1

Error Message

  • error: all
RAW_BUFFERClick to expand / collapse

Bug Description

When duplicating an Anthropic Chat Model node whose name ends with a version-like decimal string (e.g. Claude Sonnet 4.6), the duplicate is named Claude Sonnet 4. instead of the expected Claude Sonnet 4.61. It appears the deduplication logic incorrectly identifies the trailing 6 as an existing counter suffix and strips it, leaving a dangling period.

To Reproduce

  1. Add an Anthropic Chat Model node to the canvas.
  2. Rename it to Claude Sonnet 4.6.
  3. Duplicate the node (right-click => Duplicate, or Ctrl+D).
  4. Observe the name of the new node.

Expected behavior

The duplicate should be named Claude Sonnet 4.61.

Debug Info

Debug info

core

  • n8nVersion: 2.17.5
  • platform: docker (cloud)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 5
  • license: enterprise (sandbox)

storage

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

pruning

  • enabled: true
  • maxAge: 168 hours
  • maxCount: 2500 executions

client

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

Generated at: 2026-04-27T06:15:09.403Z

Operating System

n8n Cloud

n8n Version

2.17.5

Node.js Version

24.14.1

Database

SQLite (default)

Execution mode

main (default)

Hosting

n8n cloud

extent analysis

TL;DR

The issue can be resolved by adjusting the deduplication logic to correctly handle version-like decimal strings in node names.

Guidance

  • Review the deduplication logic to identify why it incorrectly identifies the trailing decimal as an existing counter suffix.
  • Verify that the issue is specific to node names with version-like decimal strings (e.g., "4.6") and does not affect other naming conventions.
  • Consider adding a special case to the deduplication logic to handle version-like decimal strings, ensuring that the entire string is preserved during duplication.
  • Test the updated deduplication logic with various node naming scenarios to ensure it works as expected.

Example

No code snippet is provided as the issue does not include specific code details.

Notes

The provided information suggests that the issue is specific to the n8n platform, version 2.17.5, and may not be applicable to other versions or environments.

Recommendation

Apply a workaround by adjusting the deduplication logic to correctly handle version-like decimal strings, as the root cause appears to be related to the logic's handling of specific naming conventions.

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 duplicate should be named Claude Sonnet 4.61.

#batch processing#GPU compatibility#latency issue#model loading#dependency error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING