n8n - 💡(How to fix) Fix Issue listing 'Version History' since 2.17.5 upgrade [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#28922Fetched 2026-04-23 07:44:10
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
commented ×1labeled ×1mentioned ×1subscribed ×1

Error Message

Describe the problem/error/question

We're seeing a new error when non-admin users try to list the Version History on their workflows.

What is the error message (if any)?

When a user opens their workflow and tries to view Version History they see an error popup that states:

  • error: all
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

We're seeing a new error when non-admin users try to list the Version History on their workflows.

This is a new issue since 2.17.5 upgrade, something that has worked before.

What is the error message (if any)?

When a user opens their workflow and tries to view Version History they see an error popup that states:

Listing all users is limited to instance administrators. Filter by project to list project members

Please share your workflow/screenshots/recording

<img width="1679" height="908" alt="Image" src="https://github.com/user-attachments/assets/e78a9739-66cf-4541-ad99-f7341fcebbe5" />

I think it would be related to this recent commit:

https://github.com/n8n-io/n8n/commit/9dfe97f8bb00f14437bc013b9ca7047804f3d70d#diff-63b83a4756e461a5010702846a92b9a64dfc564dfec0b51bc4029a3e9668af41R70

We've rolled back to 2.17.3 and all is working.

I'd love to see a quick fix for this one on account of the critical security issues fixed in 2.17.5

Debug info

core

  • n8nVersion: 2.17.5
  • platform: AWS ECS (self-hosted)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: postgres
  • executionMode: scaling (multi-main)
  • concurrency: -1
  • license: enterprise (production)

storage

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

pruning

  • enabled: true
  • maxAge: 720 hours
  • maxCount: 0 executions

client

  • userAgent: mozilla/5.0 (macintosh; intel mac os x 10.15; rv:149.0) gecko/20100101 firefox/149.0
  • isTouchDevice: false

Generated at: 2026-04-22T21:30:44.356Z

extent analysis

TL;DR

The error is likely due to a recent commit that introduced a permission check, and a quick fix would be to revert or modify this change to allow non-admin users to list version history.

Guidance

  • Review the recent commit 9dfe97f8bb00f14437bc013b9ca7047804f3d70d and assess the impact of the permission check on non-admin users.
  • Consider modifying the commit to add an exception for version history listing, allowing non-admin users to access this feature.
  • Test the modified code to ensure it resolves the issue without introducing security vulnerabilities.
  • As a temporary workaround, consider reverting to version 2.17.3, as the issue is not present in this version.

Example

No code snippet is provided, as the issue is related to a specific commit and requires a review of the code changes.

Notes

The issue is specific to version 2.17.5, and the commit in question has introduced a permission check that is causing the error. The fix will depend on the specific requirements and constraints of the application.

Recommendation

Apply a workaround by modifying the recent commit to allow non-admin users to list version history, as this will address the critical security issues fixed in 2.17.5 while resolving the current issue.

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