Three unread entries reported, but only one really, after reading, 2 unread

Some of the caching plugins also cache on the admin side of things depending on how they are configured. DB-Cache for instance can do that without the user realizing it.

We will look into it, we are already going to look into the Last Read bug with the dashboard widget so we will see if there is anything else going on with the dashboard widget that could be causing this... although this is the first it has been reported.

@illinoisharley No update, we haven't been able to replicate it on our end in order to fix it. Still working on it.

Chris, updated versions of Gravity Forms aren't going to correct the issue. Your data is out of synch, most likely due to the Database caching functionality of W3 Total Cache (which I noticed you currently have deactivated).

W3 Total Cache with Database Caching turned on can cause all sorts of data synch issues. Including the admin. For instance, it can cause problems with entry submissions which cause entry counts to be incorrect in the admin. It can also cause notifications to be incorrect because information gets cached instead of sending live data.

The problem is once your entry counts get out of synch, updated versions of the plugin aren't going to correct this because they don't do any data manipulation.

Gravity Forms will not work properly with the W3 Total Cache Database Caching turned on. You will have to use it without Database Caching.

This isn't really a bug or issue with Gravity Forms or W3 Total Cache. They are both doing what they are designed to do. Unfortunately that doesn't work properly.

This will be corrected in an upcoming version of W3 Total Cache. They are "whitelisting" the Gravity Forms related database tables so that it always goes to the database for queries instead of pulling from cache. Once this update is released you will be able to use Gravity Forms and W3 Total Cache with Database Caching turned on.

It's an issue that can cause issues with any plugin running with W3 Total Cache Database Caching that needs to get data from the database and can't rely on cache.

ANY plugin that interacts with the database and needs current data can be impacted by a database caching plugin. By their very nature, database caching is only good for primarily read only situations. However, a lot of the database caching plugins out there basically cache everything and this causes problems with other plugins.

W3 Total Cache is aware of the issue and will be updating their plugin in the near future with an update that will not interfere with Gravity Forms related data interaction.

The only we we could debug this would be to have FTP access and access to your MySQL database to look at the data directly and see what is going on. If you are comfortable with providing us with that you can do so via our Contact Us form and we can look into it.