> For the complete documentation index, see [llms.txt](https://en.help.firstline.cc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://en.help.firstline.cc/guide/issue/dian-ji-xuan-chan-xiang-mu-wu-fan-ying.md).

# Clear browser cache

When the FIRST LINE page displays abnormally, features are not updated, or the operation result is different from expected, you can refresh and log in again in order, and if necessary clear the browser cache and site data.

Browsers temporarily store website images, program files, and some site data so pages can load faster the next time you open them. After FIRST LINE is updated, if the browser is still using old cached content, you may occasionally see incomplete page display, unresponsive buttons, or features that appear not to have been updated.

However,**clearing the cache usually does not need to be the first step**. It is recommended to start with less intrusive methods first, then clear browser data further if needed.

{% hint style="info" %}
Clearing the browser cache mainly addresses situations where the browser is still loading old files or website data. If the problem is insufficient permissions, a network interruption, account settings, or restrictions on a specific function, clearing the cache usually will not solve it.
{% endhint %}

## When can you try clearing the cache?

If only your browser has the following issues and other colleagues can use FIRST LINE normally, you may consider checking cache-related causes:

* After FIRST LINE is updated, the interface still looks like the old version.
* The page displays incompletely, the layout is abnormal, or some components do not load.
* Clicking a button does nothing, and the problem continues after reopening the page.
* The same account works normally in another browser or in incognito mode.

If multiple users are experiencing the same problem at the same time, it is recommended to first check the network or system status, rather than asking each user to clear their cache one by one.

## First complete a quick check

{% stepper %}
{% step %}

### Refresh the page

First refresh FIRST LINE to let the browser reload the current page.

If it is only a temporary loading issue, you usually do not need to clear data further.
{% endstep %}

{% step %}

### Log out and log back in

If the problem still exists after refreshing, you can log out of FIRST LINE and then log in again.

This can re-establish the current login state and some page data.
{% endstep %}

{% step %}

### Test using incognito mode or another browser

Use Chrome Incognito mode, Edge InPrivate mode, or another browser to log in to FIRST LINE and test the same operation.

If it works normally in incognito mode or another browser, the issue is more likely related to the cache, cookies, extensions, or website data in the original browser.
{% endstep %}
{% endstepper %}

If the problem still persists after completing the steps above, then perform the cache-clearing action below.

## Clear the browser cache

The interface of different browsers may be adjusted with version updates, so it is recommended to follow the latest instructions provided in the browser's official documentation.

### Chrome

You can clear the cache through Chrome's "Delete browsing data" feature.

When troubleshooting FIRST LINE issues, it is recommended to first clear **"Cached images and files"**, then reopen FIRST LINE and test.

If clearing only the cache still does not work, consider clearing cookies and site data as well; after clearing this data, you may need to sign in to FIRST LINE or other websites again.

[View Chrome official help](https://support.google.com/accounts/answer/32050?hl=zh-Hant\&co=GENIE.Platform%3DDesktop)

### Microsoft Edge

In Edge's browsing data settings, you can choose the types of data and the time range to clear.

It is recommended to first clear cached data and test again; if the problem persists, clear FIRST LINE-related cookies or site data as needed.

[View Microsoft Edge official help](https://support.microsoft.com/zh-tw/edge/view-and-delete-browser-history-in-microsoft-edge)

### Firefox

Firefox can clear site cache from the Privacy & Security settings.

After clearing, reopen FIRST LINE and check whether the original operation returns to normal.

[View Firefox official help](https://support.mozilla.org/zh-TW/kb/how-clear-firefox-cache)

### Safari

Safari can clear website cache and cookies. If you use Safari, it is recommended to consult Apple's official documentation for the current operating method for your macOS and Safari versions.

[View Safari official help](https://support.apple.com/zh-tw/guide/safari/sfri11471/mac)

{% hint style="warning" %}
**Clearing cookies or site data may sign you out of websites.**

If you only want to rule out old page files, it is recommended to start with "cache" first; there is no need to delete passwords, autofill data, or all browsing history at the beginning.
{% endhint %}

## Chrome: Quickly reload the page

If you use Chrome, you can also try forcing a reload of the current page first, rather than directly clearing all browser data.

1. Open FIRST LINE.
2. Open Chrome Developer Tools.
   * Windows:`F12` or `Ctrl + Shift + I`
   * macOS:`Command + Option + I`
3. With Developer Tools open, long-press or click the reload button menu.
4. Choose the option to clear cache and reload the page.
5. Wait for the page to reload, then test the feature that was previously problematic.

{% hint style="info" %}
This method mainly targets reloading the cache for the current page, and is usually less disruptive than directly clearing all data in the entire browser.
{% endhint %}

## Still unusable after clearing

If the problem still exists after clearing the cache, it is recommended to first confirm whether the issue occurs only in your environment:

* Test using another browser or device.
* Check whether other colleagues are experiencing the same issue.
* Check whether the network connection is working properly.
* Temporarily disable browser extensions that may affect the page, then test again.

If only a specific account or a specific function cannot be used, it may also be related to account permissions, enterprise settings, or the usage conditions of the function itself; in this case, there is no need to repeatedly clear the cache.

If you still cannot determine the cause, when contacting FIRST LINE it is recommended to provide:

1. The page and feature where the problem occurred.
2. The actual error message or screen you saw.
3. The time the problem occurred.
4. The browser and device used.
5. Whether you have tested using incognito mode or another browser.

This information can help more quickly determine whether the issue comes from the browser environment, account settings, the network, or system functionality.