# Reprocess Crashes 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: 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/reprocessing-crashes.md?ask= ``` 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.