We are having a strange issue - on an Umbraco 4.9.1 site (SQL server 2008). We also have the site running on three environments but are only able to reproduce on one.

When (any) document is published - Umbraco confirms the change and updates the cache and therefore the front end website - however.... in the Content tree the modified icon shows.

On further investigation post publish umbraco calls:

/umbraco/webservices/TreeDataService.ashx?rnd=430e9f9205064804b6fabd175bade6f6&id=1114&treeType=content&contextMenu=true&isDialog=false&rnd2=31.3

Post publish which returns some JSON detailing the state of the Document in the tree something like:

{
    "data": {
      "title": "About",
      "icon": "\/umbraco\/images\/umbraco\/page_white_cup.png",
      "attributes": {
        "class": "sprTree noSpr",
        "href": "javascript:openContent('1115');",
        "umb:nodedata": "{'menu':'C:,D,MO,SK,UIR,P,Z,T5,L','nodeType':'content','source':'\/umbraco\/tree.aspx?rnd=600788d6f7684957abe744ac6be63b03\\u0026id=1115\\u0026treeType=content\\u0026contextMenu=true\\u0026isDialog=false'}"
      }
    },
    "attributes": {
      "id": "1115",
      "class": "overlay-new",
      "rel": "dataNode",
      "umb:type": "content"
    }
  },

The key thing being that the treeservice is telling Umbraco to add the overlay-new class to the document container div in the DOM.

The environment is pretty slow - is anyone aware of this issue - or maybe any issues of synchronisation between publish and updating the GUI?

Any thoughts would be appreciated - most useful would be the process that Umbraco undertakes to determine whether a given version of a document is the most recent.

Our next step is to start hacking apart the tree service which would prefer not to :)

Many Thanks for any input.