ROES Web - Empty Browser Cache and Hard Reload (Chrome)
ROES Web – Empty Browser Cache and Hard Reload in Chrome
Use this article when ROES Web needs to be refreshed in Chrome after CSS changes, configuration updates, or unwanted cached results.
Overview
Chrome may continue using cached ROES Web files even after changes have been made to CSS, content, labels, or configuration. An Empty Cache and Hard Reload forces Chrome to discard cached files for the current page and reload ROES Web from the server.
Symptoms
- ROES Web still shows older CSS or styling after a change.
- ROES Web shows outdated labels, messages, or content.
- A recently changed ROES Web configuration does not appear in Chrome.
- Support needs the browser to reload ROES Web without using cached page resources.
Before You Begin
- These steps apply to Google Chrome.
- Open the ROES Web page that needs to be refreshed before starting.
- Developer Tools must be open for the special reload options to appear.
- This clears cached page resources for the current site reload. It does not delete ROES orders or customer image files.
Solution
Open ROES Web in Chrome
In Google Chrome, go to the ROES Web page that needs to be refreshed.
Open Chrome Developer Tools
Open Developer Tools using one of the following methods:
- Windows / Linux: press Ctrl + Shift + I.
- Mac: press Command + Option + I.
- Or use Chrome’s menu: More Tools > Developer Tools.
Open the reload menu
With Developer Tools still open, right-click or click-and-hold the browser reload button next to the address bar.
Choose Empty Cache and Hard Reload
From the reload menu, choose Empty Cache and Hard Reload.
Review ROES Web after reload
After the page reloads, confirm that the expected CSS, content, labels, or configuration changes are now visible.
Important Chrome Note
The Empty Cache and Hard Reload option only appears when Chrome Developer Tools are open. If the reload menu only shows the normal reload options, open Developer Tools and try again.
Expected Result
Chrome should reload ROES Web without using the previously cached page resources. Any recent ROES Web CSS, content, or configuration changes should display after the reload if the server-side changes are correct.
Escalation Notes
- Confirm the customer is using Google Chrome.
- Confirm Developer Tools were open when the hard reload was performed.
- Ask what specific change is still not appearing after the reload.
- Confirm whether the issue also appears in an incognito window or another browser.
- If CSS or content changes still do not appear, verify that the change was published to the correct ROES Web client/location.