n8n - 💡(How to fix) Fix Since 2.15.0: g.value.toLowerCase is not a function > Input and output data of nodes not loading anymore [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#28296Fetched 2026-04-11 06:30:53
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×3commented ×1mentioned ×1subscribed ×1
RAW_BUFFERClick to expand / collapse

Bug Description

Since 2.15.0: g.value.toLowerCase is not a function > Input and output data of nodes not loading anymore

<img width="1895" height="835" alt="Image" src="https://github.com/user-attachments/assets/83f800e4-3880-49ad-aa87-5c82970e482f" />

To Reproduce

Simply run a flow or a part of a flow in the editor and then try to open a node that just ran. It won't load it's input and output data.

Expected behavior

Load input and output data as expected.

Debug Info

Debug info

core

  • n8nVersion: 2.15.0
  • docker (self-hosted)

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: true

Operating System

Windows

n8n Version

2.15.0

Node.js Version

24.13.1

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted

extent analysis

TL;DR

  • The issue with g.value.toLowerCase is not a function suggests a type mismatch, and checking the data type of g.value before calling toLowerCase() might resolve the issue.

Guidance

  • Verify the data type of g.value to ensure it's a string before attempting to call toLowerCase() on it.
  • Check if there are any recent changes in the data processing pipeline that could be causing g.value to be non-string.
  • Inspect the input and output data of nodes to identify any patterns or inconsistencies that might be contributing to the error.
  • Consider adding a type check or a default value for g.value to prevent the error from occurring.

Example

  • A simple type check could be implemented as if (typeof g.value === 'string') { g.value = g.value.toLowerCase(); }.

Notes

  • The root cause of the issue is unclear without more information about the data being processed, but the error message suggests a type mismatch.
  • This solution assumes that g.value is expected to be a string, but this might not always be the case.

Recommendation

  • Apply workaround: Add a type check for g.value before calling toLowerCase() to prevent the error from occurring, as the root cause is unclear and this will prevent the application from crashing.

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

Load input and output data as expected.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING