(05-24-2016, 05:43 PM)twpmarketing Wrote: Duh, sorry, not thinking today. I hate it when something works as it should, but doesn't give a clue why it changed.
If the robot visits your site, thus triggering a new session, it can read the session ID but still triggers a session test within seconds of the first. I don't know enough about how a typical robot is coded to know why that would happen. A question becomes: is it the robot that is triggering the second session check or is it done by CI?
I'll look at the access log if it happens again. Another thing I forgot to mention is that I cleared out all of the session records in the database. I think it's more likely that that has something to do with why the errors stopped than anything else.
