Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix Bug The conflicting workflow ID `TcOR8zUz95Ufi2pq` does not appear in the workflows list. Clicking the link in the error message leads to a page saying the workflow does not exist. There is only one workflow in the workspace. [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#28210•Fetched 2026-04-09 08:16:07
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
thiago09864thiago09864
Participants
n8n-assistant[bot]n8n-assistant[bot]thiago09864thiago09864
Timeline (top)
commented ×1labeled ×1mentioned ×1subscribed ×1

Error Message

Describe the problem/error/question

When trying to activate a workflow, n8n shows a "Conflicting Trigger Path" error referencing a workflow ID (TcOR8zUz95Ufi2pq) that does not exist in the workspace. The workflow cannot be found in the workflows list, cannot be accessed via direct URL, yet it blocks activation of any new workflow using the same Telegram Trigger.

What is the error message (if any)?

The conflicting workflow ID TcOR8zUz95Ufi2pq does not appear in the workflows list. Clicking the link in the error message leads to a page saying the workflow does not exist. There is only one workflow in the workspace. The error persists even after:

  • error: all
RAW_BUFFERClick to expand / collapse

Describe the problem/error/question

When trying to activate a workflow, n8n shows a "Conflicting Trigger Path" error referencing a workflow ID (TcOR8zUz95Ufi2pq) that does not exist in the workspace. The workflow cannot be found in the workflows list, cannot be accessed via direct URL, yet it blocks activation of any new workflow using the same Telegram Trigger.

What is the error message (if any)?

A trigger 'Telegram Trigger' in the workflow 'TcOR8zUz95Ufi2pq' uses a conflicting URL path, so this workflow cannot be activated. You can deactivate TcOR8zUz95Ufi2pq and activate this one, or insert a new trigger node of the same type in either workflow.

Please share your workflow/screenshots/recording

The conflicting workflow ID TcOR8zUz95Ufi2pq does not appear in the workflows list. Clicking the link in the error message leads to a page saying the workflow does not exist. There is only one workflow in the workspace.

The error persists even after:

  • Creating a new Telegram bot with a different token
  • Changing the webhook path to a unique value (pushinpay-sophia-v8)
  • Confirming no other workflows exist in the workspace

Share the output returned by the last node

Workflow cannot be activated — no execution output available.

Debug info

core

  • n8nVersion: 2.14.2
  • platform: docker (cloud)
  • nodeJsVersion: 24.13.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 (x11; linux x86_64) applewebkit/537.36 (khtml, like gecko) chrome/146.0.0.0 safari/537.36
  • isTouchDevice: true

Generated at: 2026-04-08T17:51:26.660Z

Expected behavior

Deleted or non-existent workflows should not block activation of new workflows. The system should clean up orphaned webhook/trigger registrations when a workflow is deleted.

extent analysis

TL;DR

The most likely fix is to manually remove the orphaned trigger registration for the non-existent workflow TcOR8zUz95Ufi2pq from the database or storage.

Guidance

  • Investigate the database (sqlite) for any remaining entries related to the workflow TcOR8zUz95Ufi2pq, specifically in tables related to triggers or workflows.
  • Check the storage (filesystem) for any files or configurations that might be referencing the non-existent workflow.
  • Consider running a database cleanup or pruning task to remove any orphaned entries, if available in the n8n version (2.14.2).
  • If using the enterprise license, check the documentation for any specific guidance on handling orphaned workflows or triggers.

Example

No specific code example is provided as it would require more information about the database schema and storage configuration.

Notes

The issue seems to be related to the database or storage not being properly cleaned up after a workflow is deleted. The provided debug information suggests that the pruning feature is enabled, but it might not be effectively removing all references to deleted workflows.

Recommendation

Apply a workaround by manually removing the orphaned trigger registration, as upgrading to a fixed version is not explicitly implied in the issue. The reason is that the issue seems to be related to a specific configuration or data corruption rather than a version-specific bug.

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

Deleted or non-existent workflows should not block activation of new workflows. The system should clean up orphaned webhook/trigger registrations when a workflow is deleted.

#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

n8n - 💡(How to fix) Fix Bug The conflicting workflow ID `TcOR8zUz95Ufi2pq` does not appear in the workflows list. Clicking the link in the error message leads to a page saying the workflow does not exist. There is only one workflow in the workspace. [1 comments, 2 participants]