Whenever we push updates to our site, we push from Visual Studio to a deployment slot on Azure and then swap the slot to the production slot. For the most part it works well, however we frequently have problems with nodes and documents dropping out of the cache.
When we check them in the CMS they are still published, but they are not showing up on internal search or where they should be filtered onto a page that aggregates child content. Republishing the file solves the problem.
Unfortunately republishing the entire site doesn't, so we are left with waiting until a user complains about missing content and then individually republishing the files.
Documents dropping out of cache
Whenever we push updates to our site, we push from Visual Studio to a deployment slot on Azure and then swap the slot to the production slot. For the most part it works well, however we frequently have problems with nodes and documents dropping out of the cache.
When we check them in the CMS they are still published, but they are not showing up on internal search or where they should be filtered onto a page that aggregates child content. Republishing the file solves the problem.
Unfortunately republishing the entire site doesn't, so we are left with waiting until a user complains about missing content and then individually republishing the files.
Has anyone come across this and have a solution?
is working on a reply...