Denying access due to session lacking permission to transcode key

[Healzangels]

Server Version#: Version 1.32.6.7468
Player Version#: Version 4.108.0
OS: unRaid 6.11.5
[Req#18c0/Transcode] Denying access due to session lacking permission to transcode key /library/metadata/408645

Greetings!
Today I’ve started noticing my console logs being flooded with the warning message above. Nothing appears to actually be wrong/acting up but seeing the error is a bit alarming.

The message appears every 3 seconds or so. I have confirmed the item in question via the 408645 ID. It’s a TV show which I can confirm is not being actively streamed but was recently.
Trying to play the episode does not seem to result in any playback issues.

Things I’ve tried so far:
Restart Docker Container + Restart Host
Updating to the latest beta version of Plex from the latest stable release.
Downgrading back down to version-1.29.2.6364-6d72b0cf6
Confirm both host and docker container have full 777 permissions on the /tmp location.
Changing my transcode directory from it’s current ram location to a location on an ssd.
Run DB repair Scripts + Restored from an older version of DB
Delete Codecs folder and allow to recreate.

I also tried doing a “plex dance” on the item in question but this caused a new error to be present in the console which I unfortunately didn’t capture before restoring my DB but certainly can reproduce for troubleshooting.

All things still lead to the error popping up every 3 seconds or so. Hoping may be able to get some assistance here in tracking down the root cause or at least making it stop.
Thanks!

[Healzangels]

Additional things I’ve tried:
Turning off HW transcoding
Disabling Transcoding all together with.
Also restarting Docker container between each test but warning continues.

[ChuckPa]

1. Confirm permissions on the file itself and the containing directory
2. Scan files
3. Refresh Metadata
4. Analyze

If this were a permissions problem with transcode directories, all transcodes would fail.

[Healzangels]

Hey ChuckPA! Thanks so much for the follow up on a weekend (plus your awesome DB repair script)

As a typical quirky issue goes I woke up with morning to check the console and there was suddenly no trace of the warning message!

I’m thinking the 2-5 Maintenance may have ended up doing your suggestion 2-4 which most likely was the fix. (I swear I tried those but happy to see it gone )

Thanks again for the assistance!