Refresh or Update a Cache

Refresh a Cache for a site collection

This gives an overview of how to kick-off the Work Cache update which processes the Work Cache update queue, and how to perfom a full refresh of the caches, namely Work Cache, Project Cache and Project Status Report Cache for the entire site collection.

Reasons for performing a Refresh of a Cache:

Permission changes: Adding or removing a person or group to a site requires a Refresh. Adding a person to an existing group does not require a Refresh and therefore is the recommended way to add users.
Restoring items from the Recycle Bin.
Renaming a Project Site.
Renaming a work list.

The Work Cache has two timer jobs that maintain it and ensure that the content is as current as possible. The Project Cache and Project Status Report Cache have one timer job each to refresh their content. Updates are carried out in real-time.

If these have run recently, running them manually might not be needed so details on their frequency and last run time are displayed on the page.

To manually run any of these actions:

Note: You need to be a Site Collection Administrator or a member of the BrightWork Cache Administrator's user group to perform this task.

Navigate to the site collection home page and click Settings | Site Settings.
Click Refresh BrightWork Caches.

Update Work Cache

Update pushes any recent changes to the cache while refresh does a full rebuild of the cache.

Tip! Update is much faster than refresh and should be used to update the Work Cache unless one of the reasons listed above necessitates a full Refresh.

To run an Update of the Cache click the link to Apply the queued updates for this site collection to the work cache and then click OK to confirm.

You can also run the Refresh Project, Project Status Report, or Work Cache for the site at the site level. This will ensure that all changes in that site and below are accounted for.

Last updated refers to when the Work Cache was last updated by the update timer job.

Refresh Work Cache

Tip! The quickest way to Refresh Project Data including the Work Cache is using the Project Ribbon.

Refreshing all the contents of the entire Work Cache may take some time depending on the size of the Work Cache and site collection.

To start the Refresh of the Cache click the link to Perform a full work cache refresh for this site collection and then click OK to confirm.

Refresh Project Cache

Refreshing all the contents of the entire Project Cache may take some time depending on the size of the Project Cache and site collection.

To start the Refresh of the Cache click the link to Perform a full project cache refresh for this site collection and then click OK to confirm.

Refresh Project Status Report Cache

Refreshing all the contents of the entire Project Status Report Cache may take some time depending on the size of the site collection.

To start the Refresh of the Project Status Report Cache click the link to Perform a full project status report cache refresh for this site collection and then click OK to confirm.

Timer Jobs

The Project Cache, Project Status Report Cache, and Work Cache are all maintained by timer jobs.

Work Cache

BrightWork Work Cache Update Processing Timer Job (Every 15 minutes)
Update is for processing items in the Work Cache queue and is the recommended way to update the Work Cache queue.
BrightWork Work Cache Refresh Timer Job (Daily)
Refreshing the Work Cache will traverse the hierarchy updating the Work Cache with any changes it finds. This is useful to do on a periodic basis and normally happens on a schedule everyday but it can be triggered manually. This can take a long time to run depending on the size of the hierarchy, the number of open items in the hierarchy, and other factors.

If a large number of items are getting added to the Work Cache the page might time out. The page will time out after 2 hours, if this happens you should re-run the Refresh or use the timer job.

Project Cache

BrightWork Project Cache Refresh Timer Job (Daily)
Refreshing the Project Cache will traverse the hierarchy updating the cache with any changes it finds. This typically runs nightly.

Project Status Report Cache

BrightWork Project Status Report Cache Refresh Timer Job (Daily)
Refreshing the Project Status Report Cache will traverse the hierarchy updating the cache with any changes it finds. This typically runs nightly.

Troubleshooting

Data Not Added To a Cache

If a project site's data is not added to a cache, check if it or any of the sites above it in the site hierarchy are marked as either Archived or Completed. For example, this circumstance could occur if a Project Office is marked as Completed when it still has project sites under it that are not Completed.

Page Time Out

If the page times out, contact your SharePoint administrator as they can run the refresh using the timer job on the server (though this will run on all BrightWork Site collections not just your one). Alternatively your SharePoint administrator can use PowerShell to run refreshes of the Work, Project, or Project Status Report caches targeting specific site collections using the commands below:

Refresh-BWProjectCache [-Identity] <SPSitePipeBind>

Refresh-BWWorkCache [-Identity] <SPSitePipeBind>

Refresh-BWPSRCache [-Identity] <SPSitePipeBind>

For example these commands will refresh the specified caches:

Refresh-BWProjectCache https://myserver/sites/my-bw-sitecollection

Refresh-BWWorkCache https://myserver/sites/my-bw-sitecollection

Refresh-BWPSRCache https://myserver/sites/my-bw-sitecollection

These commands will refresh the specified caches and also write the details to the SharePoint logs:

Refresh-BWProjectCache https://myserver/sites/my-bw-sitecollection -verbose

Refresh-BWWorkCache https://myserver/sites/my-bw-sitecollection -verbose

Refresh-BWPSRCache https://myserver/sites/my-bw-sitecollection -verbose