Constant plex queryParser: Invalid field XXX found, ignoring in logs

Plex Media Server
1

I’ve noticed that the logs constantly have a repeating WARN for Invalid field, ignoring. It doesn’t seem to be causing any issues, but figured i would hsare this as i couldn’t see any other topics around this.

Server Version#: 1.30.1.6497
Player Version#: 4.87.2

Jan 02, 2023 02:32:53.073 [0x7f7efcdb4b38] WARN - [Req#36b] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Jan 02, 2023 02:32:53.074 [0x7f7efcdb4b38] WARN - [Req#36b] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Jan 02, 2023 02:32:53.076 [0x7f7efda0cb38] WARN - [Req#369] QueryParser: Invalid field ‘sectionID’ found, ignoring.
Jan 02, 2023 02:32:53.077 [0x7f7efda0cb38] WARN - [Req#369] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Jan 02, 2023 02:32:53.077 [0x7f7efda0cb38] WARN - [Req#369] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Jan 02, 2023 02:32:53.085 [0x7f7ef1059b38] WARN - [Req#36e] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Jan 02, 2023 02:32:53.086 [0x7f7ef1059b38] WARN - [Req#36e] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Jan 02, 2023 02:32:53.095 [0x7f7ef9365b38] WARN - [Req#36d] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Jan 02, 2023 02:32:53.096 [0x7f7ef9365b38] WARN - [Req#36d] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Jan 02, 2023 02:32:53.096 [0x7f7ef0dd6b38] WARN - [Req#36f] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Jan 02, 2023 02:32:53.097 [0x7f7ef0dd6b38] WARN - [Req#36f] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.

2

You can ignore .

You’re seeing work in progress which isn’t fully implemented yet.
It’s harmless at this point/

1 Like
3

good to know! :slight_smile: