> For the complete documentation index, see [llms.txt](https://docs.bugsplat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugsplat.com/education/how-tos/reprocessing-crashes.md). # Reprocess Crashes BugSplat can reprocess crashes that were processed incorrectly due to missing symbols, mismatched symbols, or errors during initial processing. BugSplat processes crashes in two different modes, **Normal** and **Debug**. All crashes are processed in normal mode, and specific actions, such as requesting modules or debugger output will trigger the crash to process again in debug mode. Sometimes, you may want to manually reprocess a crash if you recently uploaded new symbols or if your crash was not processed correctly. You can use the **Reprocess** button on the **Crash** page to kick off a reprocess operation manually The **Reprocess** button will be disabled if the platform type does not support reprocessing. BugSplat limits the concurrent reprocess operations for any given database to 50. If necessary, you can contact , and our support team can assist you with deleting bulk sets of crashes larger than 50. --- # 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://docs.bugsplat.com/education/how-tos/reprocessing-crashes.md?ask=&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.