n8n - 💡(How to fix) Fix specially showing: Requested version 20250401 is not active [2 comments, 3 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#28667Fetched 2026-04-20 12:15:11
View on GitHub
Comments
2
Participants
3
Timeline
4
Reactions
0
Timeline (top)
commented ×2closed ×1labeled ×1
RAW_BUFFERClick to expand / collapse

Bug Description

specially showing:

Requested version 20250401 is not active

To Reproduce

specially showing:

Requested version 20250401 is not active

Expected behavior

specially showing:

Requested version 20250401 is not active while executing the work flow

Debug Info

specially showing:

Requested version 20250401 is not active

Operating System

specially showing: Requested version 20250401 is not active

n8n Version

specially showing: Requested version 20250401 is not active

Node.js Version

specially showing: Requested version 20250401 is not active

Database

SQLite (default)

Execution mode

main (default)

Hosting

n8n cloud

extent analysis

TL;DR

The issue is likely due to an inactive version, and checking the version status or updating to an active version may resolve the problem.

Guidance

  • Verify the status of version 20250401 to confirm it is indeed inactive.
  • Check the documentation or support resources for n8n cloud to understand how to activate a version or update to a different active version.
  • Review the workflow configuration to ensure it is set to use an active version, if possible.
  • Consider reaching out to n8n cloud support for assistance with activating the required version or finding an alternative solution.

Notes

The provided information is limited, and without further details about version management in n8n cloud, it's challenging to provide a more specific fix. The issue seems to be related to version management rather than a code or configuration problem.

Recommendation

Apply workaround: Check with n8n cloud support to activate the required version or find an alternative active version that can be used with the current workflow.

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

specially showing:

Requested version 20250401 is not active while executing the work flow

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 specially showing: Requested version 20250401 is not active [2 comments, 3 participants]