Network Resources Always Shows 0 (Inaccurate) - NS Log Shows Error Parsing Network Resources

Newly installed this NS last week.
I do not think I've ever seen the Network Resources as anything other than '0', but that is not accurate.

I have ~187 Network Resources; here's a quick snippet of some of those so you don't have to take my word:

When looking at the NS log (just in default 'Warning' level), I see Network Resources constantly as an error; I went ahead and restarted the NS to get a piece of the log before the restart (showing the existing / recurring Network Resources error, the restart, and the re-emergence of the Network Resources error again):

2023-08-30 19:45:16 error: NS: processNetworkResources Error
2023-08-30 19:45:37 warn: POLY: Received stop message
2023-08-30 19:45:45 info: NS: Starting Node Server
2023-08-30 19:45:45 info: POLY: Interface starting
2023-08-30 19:45:45 info: POLY: Getting config from environment
2023-08-30 19:45:45 info: POLY: MQTT client connected
2023-08-30 19:45:45 info: NS: MQTT Connection started
2023-08-30 19:45:45 error: POLY: Config has logLevel: WARNING
2023-08-30 19:45:45 warn: POLY: Loglevel: warn
2023-08-30 19:46:10 error: NS: processNetworkResources Error

If I put it into Debug level, and hit Discover, the log looks more like this:

2023-08-30 19:52:11 debug: NS: Message Received: { discover: {} }
2023-08-30 19:52:11 debug: NS: Discover Nodes
2023-08-30 19:52:11 info: NS: Discovering Nodes
2023-08-30 19:52:14 debug: NS: Discover Integer Vars
2023-08-30 19:52:16 debug: NS: Discover State Vars
2023-08-30 19:52:18 debug: NS: Discover Programs
2023-08-30 19:52:20 debug: NS: Discover Network Resources
2023-08-30 19:52:22 debug: NS: Discover Error Log Entries
2023-08-30 19:52:26 info: NS: Checking node: 4C ...
...
2023-08-30 19:52:26 info: NS: Checking node: n001_zzfk93868
2023-08-30 19:52:35 error: NS: processNetworkResources Error
2023-08-30 19:52:37 info: POLY: Setting node controller driver GV10: ...