n8n - 💡(How to fix) Fix Clicking workflow in list redirects to blank "My workflow" with ?new=true instead of opening existing workflow [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#29769Fetched 2026-05-06 06:35:21
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×3commented ×1mentioned ×1subscribed ×1

Error Message

Describe the problem/error/question

What is the error message (if any)?

No error message. Silent redirect to new blank workflow.

  • error: all
RAW_BUFFERClick to expand / collapse

Describe the problem/error/question

Clicking a workflow in the workflow list does not open it. Instead, n8n redirects to a new blank canvas at a completely different workflow ID with ?new=true appended. The title shows "My workflow" instead of the clicked workflow's name. Affects multiple workflows in my account but not all of them.

What is the error message (if any)?

No error message. Silent redirect to new blank workflow.

Please share your workflow/screenshots/recording

See screenshots attached: (1) workflow list showing the workflow, (2) blank canvas after clicking it, URL bar shows ?new=true with a different workflow ID than the one clicked.

<img width="1491" height="399" alt="Image" src="https://github.com/user-attachments/assets/27f06ac6-cc7d-4138-93d9-e9760f5e8688" /> <img width="2360" height="1320" alt="Image" src="https://github.com/user-attachments/assets/facb1a36-797e-412e-b774-0c20080e4d1e" />

Share the output returned by the last node

N/A — canvas never loads. Confirmed via REST API (GET /api/v1/workflows/{id}) that workflow data is intact. Executions triggered via webhook succeed normally.

Debug info

core

  • n8nVersion: 2.19.2
  • 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/147.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-05-05T10:08:26.982Z

Additional context

  • Affected workflows are inside a subfolder ("DRC Workflows") under Personal — may be related to subfolder routing
  • Hard refresh (Ctrl+Shift+R) did not resolve
  • New Chrome profile did not resolve
  • Issue started 2026-05-05 after the May 4 cloud availability incident was marked resolved

extent analysis

TL;DR

The issue might be related to subfolder routing, and checking the workflow ID and subfolder configuration could help resolve the silent redirect to a new blank workflow.

Guidance

  • Verify that the workflow IDs in the URL match the expected workflow IDs, and check for any inconsistencies in the subfolder structure.
  • Investigate the routing configuration for workflows inside subfolders, specifically the "DRC Workflows" subfolder, to ensure it is correctly set up.
  • Try accessing the affected workflows using the REST API (GET /api/v1/workflows/{id}) to see if the issue is specific to the UI or a more general problem.
  • Check the n8n documentation for any known issues or configuration requirements related to subfolder routing and workflow IDs.

Notes

The issue seems to be specific to certain workflows and subfolders, and the provided information suggests a potential routing or configuration issue. However, without more detailed information about the n8n configuration and workflow setup, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Try reconfiguring the subfolder structure or workflow IDs to see if it resolves the issue, as the problem might be related to the specific setup of the affected workflows.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING