chris7606945629
Your log is too big.
Close SF, delete the streamfab.log and just analyze Judy Justice, and then close SF and attach the log.
I can see, though, all the way down to episode 26:
2026:03:06-15:14:59 0×000068f0 [Info]: [RFC.amazon] find playbackActions entitlementType : “PRIME_SUBSCRIPTION”
2026:03:06-15:14:59 0×000068f0 [Info]: [RFC.amazon] ignore episode: 26 titleID: “B0G3Z6CMJP” bEntitlement: false bFoundEntitlementType:
Still could be an Amazon issue, as:
https://downdetector.com/status/amazon/
ALSO ADDED: None of us had such issues with Judy Justice or Tribunal Justice till Amazon started freaking around with the layouts. And the layout changes seem to have affected these 2 programs the most.
I started to blame Amazon as usual, but then overthinking: I say, is it Judy Sheindlin? As she controls both programs.
Both programs are produced by Sheindlin and her production team.
I myself, when it first started, was in messages with support, and Wilson with sending HTML code and screenshots.
At the end when the first fix came, I was told they finally got access to the format changes so could then start to make fixes.
The new fixes in 7016 work for most, so I guess get streamfab.log; what might help too is the python.log. Delete both, then open SF and just analyze Judy Justice and attach them. Or maybe also try logging out of Amazon and log back in, or even better, clear all cache, temp folders, and cookies.
And also check if the Amazon issues are fully cleared up via downdetector.
