View Single Post
In fairness to Sneaky Peek 1.6.1, I had this issue a few weeks ago and rebuilt the database which seemed like it had fixed the problem.