@haydenjames Just following up on this, would you be able to check your logs to see if that warning has cropped up again?
Looking at it again now it seems the logging is accurate, albeit it should be a warning rather than an error, and it needs additional data (like the post causing it), however I’m not sure I’m capturing all scenarios in the test.