> For the complete documentation index, see [llms.txt](https://coldbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coldbox.ortusbooks.com/v5.x-1/digging-deeper/recipes/clearing-the-view-cache.md).

# Clearing the View Cache

## Introduction

If you use any of the view partial caching mechanisms in Coldbox either through `setView()` or`renderView()` you might be asking yourself:

> Is there an easy, programmatic way to remove a specific element from the view cache?

The answer is, of course! All view and event caching occurs in a cache provider called template and you can retrieve it like so from your handlers, layouts, views, plugins and interceptors:

```javascript
var cache = cachebox.getCache("template");
```

You can also use the WireBox injection DSL

```javascript
property name="cache" inject="cachebox:template">
```

## Clearing methods

There are a few methods that will help you clear views:

* `clearView(viewSnippet)` - Clear views with a snippet
* `clearAllViews(async)` - Clear all views
* `clearViewMulti(viewSnippets)` - Clear multiple view snippets with a list or array of snippets

```javascript
getCache( "template" ).clearView('home');
```

Very easy! Just send in what you need and it will be purged.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://coldbox.ortusbooks.com/v5.x-1/digging-deeper/recipes/clearing-the-view-cache.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.