# Remove Crashes

When working with new tools, it can take a few rounds of trial and error before you get things exactly right. In BugSplat, sometimes this means posting a crash from a test application or otherwise creating clutter in your workspace. Never fear! BugSplat allows you to batch remove clutter from your database.

{% hint style="danger" %}
Removing crashes is a destructive action that can't be undone. Tread carefully!
{% endhint %}

### Steps 🥾

1. Navigate to the [Crashes](https://app.bugsplat.com/v2/crashes) page and select your BugSplat database
2. Filter and sort to a list of crashes that you would like to remove
3. Carefully review the list of crashes in your current view. All crashes in the current view will be removed from your database.
4. Click the **🗑️ Delete** button to load a confirmation modal
5. Click **Delete** in the confirmation modal to delete your crashes

**Note:** deleting crashes should be done sparingly in the case of mistakes. If you'd like to stop processing crashes for a specific version, consider using the retire crashes feature or create a new database instead.

<figure><img src="/files/FG4fZmm0PSPLHsQ7qzhe" alt=""><figcaption><p>Deleting Invalid Crash Reports</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bugsplat.com/education/how-tos/remove-crashes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.