# \[warn\] Skipping field 'value': unsupported type object
**URL:** https://discourse.nodered.org/t/warn-skipping-field-value-unsupported-type-object/100403
**Category:** General
**Created:** [18 February 2026 07:40 UTC](https://discourse.nodered.org/t/warn-skipping-field-value-unsupported-type-object/100403 "2026-02-18T07:40:19Z")
**Posts on this page:** 15
**Page:** 1
### Author:  [@svefro](https://discourse.nodered.org/u/svefro)
#### Post date: [18 February 2026 07:40 UTC](https://discourse.nodered.org/t/warn-skipping-field-value-unsupported-type-object/100403/1 "2026-02-18T07:40:19Z")
i'm getting this warning in the console and the online debug window sometimes.
`18 Feb 08:33:41 - [warn] Skipping field 'value': unsupported type object`
My project is HUGE (flows.json is 3.8Mb). So it is hard to track down.
There is no other info about where this message is coming from in the output
Is there a way to find out? can i enable more debug info?
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [18 February 2026 11:12 UTC](https://discourse.nodered.org/t/warn-skipping-field-value-unsupported-type-object/100403/2 "2026-02-18T11:12:31Z")
Should also appear in the Node-RED log. You may need to up the logging level to get more clues.
---
### Author:  [@svefro](https://discourse.nodered.org/u/svefro)
#### Post date: [18 February 2026 13:41 UTC](https://discourse.nodered.org/t/warn-skipping-field-value-unsupported-type-object/100403/3 "2026-02-18T13:41:56Z")
I changed logging to trace. but get the same output.
i'm using "node-red-log".
is there a log with more details than that somewhere?
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [18 February 2026 14:27 UTC](https://discourse.nodered.org/t/warn-skipping-field-value-unsupported-type-object/100403/4 "2026-02-18T14:27:04Z")
With trace, you should at least get an idea of where in your processes the warning is being generated. You could also turn on the audit feature of the log though the output can be rather crazy. There is no other log.
You might also think about what nodes you have installed. Generally disconnected warnings and errors come from contributed nodes but looking at that one, could it possibly be from Dashboard 2?
Next steps will be trying to disable parts of your flows or doing a filing system search through your userDir folder (including the node\_modules folder) for the text "Skipping field". It's a long slog though unfortunately.
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [18 February 2026 14:30 UTC](https://discourse.nodered.org/t/warn-skipping-field-value-unsupported-type-object/100403/5 "2026-02-18T14:30:29Z")
That message is not one Node-RED core outputs so it is either written in your flows or coming from a contrib package.
Have you searched your flows (`CTRL-F`) for `Skipping`?
---
### Author:  [@svefro](https://discourse.nodered.org/u/svefro)
#### Post date: [18 February 2026 14:49 UTC](https://discourse.nodered.org/t/warn-skipping-field-value-unsupported-type-object/100403/6 "2026-02-18T14:49:58Z")
Yes i have. no results.
searched the source of the suspected contrib node
and here it is. the debug output should show where the warning comes from.
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [18 February 2026 15:05 UTC](https://discourse.nodered.org/t/warn-skipping-field-value-unsupported-type-object/100403/7 "2026-02-18T15:05:42Z")
> [@svefro](#):
>
> the debug output should show where the warning comes from
Ideally it would. But this is a limitation of how node.js works. Sometimes, things are so deeply embedded that Node-RED cannot know where the message came from. In my nodes, I always make sure that every message is prefixed with the node name and function name, somthing like this: `[nodename:fnname] Some error`.
---
### Author:  [@svefro](https://discourse.nodered.org/u/svefro)
#### Post date: [18 February 2026 18:36 UTC](https://discourse.nodered.org/t/warn-skipping-field-value-unsupported-type-object/100403/8 "2026-02-18T18:36:55Z")
that's a good practice
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [18 February 2026 20:16 UTC](https://discourse.nodered.org/t/warn-skipping-field-value-unsupported-type-object/100403/9 "2026-02-18T20:16:24Z")
If you've the time, you should raise an issue against that repo.
---
### Author:  [@svefro](https://discourse.nodered.org/u/svefro)
#### Post date: [18 February 2026 20:38 UTC](https://discourse.nodered.org/t/warn-skipping-field-value-unsupported-type-object/100403/10 "2026-02-18T20:38:24Z")
Already done. Thanks 🙂
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [18 February 2026 22:18 UTC](https://discourse.nodered.org/t/warn-skipping-field-value-unsupported-type-object/100403/11 "2026-02-18T22:18:39Z")
Does node-red-contrib-influxdb not work with v3?
---
### Author:  [@svefro](https://discourse.nodered.org/u/svefro)
#### Post date: [19 February 2026 14:58 UTC](https://discourse.nodered.org/t/warn-skipping-field-value-unsupported-type-object/100403/12 "2026-02-19T14:58:08Z")
No
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [19 February 2026 16:41 UTC](https://discourse.nodered.org/t/warn-skipping-field-value-unsupported-type-object/100403/13 "2026-02-19T16:41:40Z")
Have you tried it? I suspect that the API for v1 is upwards compatible to 3.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [20 February 2026 09:03 UTC](https://discourse.nodered.org/t/warn-skipping-field-value-unsupported-type-object/100403/14 "2026-02-20T09:03:15Z")
If you add a Debug node showing what is being sent to the node, set it to Output Complete Message and to Send to Console then it will log all the messages you send it in the node red log. Then after it occurs you can look back through the log and see what you sent it. The warning suggests that you are sending an object to the value field.
Note that the warning from the node may appear immediately before you debug information as the message into the debug node may be serviced after it is handled by the influx node.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [21 May 2026 09:03 UTC](https://discourse.nodered.org/t/warn-skipping-field-value-unsupported-type-object/100403/15 "2026-05-21T09:03:31Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.