# Zammad web UI slow / detailed documentation missing: How to troubleshoot?

**URL:** https://community.zammad.org/t/zammad-web-ui-slow-detailed-documentation-missing-how-to-troubleshoot/10713
**Category:** Technical assistance
**Created:** [January 9, 2023, 3:41pm UTC](https://community.zammad.org/t/zammad-web-ui-slow-detailed-documentation-missing-how-to-troubleshoot/10713 "2023-01-09T15:41:26Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Stubenhocker](https://community.zammad.org/user_avatar/community.zammad.org/stubenhocker/32/3944_2.png) [@Stubenhocker](https://community.zammad.org/u/Stubenhocker)
#### Post date: [January 20, 2023, 4:03pm UTC](https://community.zammad.org/t/zammad-web-ui-slow-detailed-documentation-missing-how-to-troubleshoot/10713/5 "2023-01-20T16:03:24Z")

</div>

For the unprocessable emails you can check this community post:

> [@Unprocessable mails](https://community.zammad.org/t/unprocessable-mails/779/5):
>
> You can bounce broken E-Mails to “force” a new fetch to zammad - especially in your case that should work. If you do not want to do that, you can use the content of the E-Mail under /opt/zammad/var/spool/unprocessable\_mail/ to add the E-Mails content to a manual ticket. That’s how I’ve done it with 1 Ticket. slight_smile Edit: After that you can delete the E-Mail from the zammad tmp-directory without any danger. Edit2: Prior Zammad 6.0 those Emails where located within /opt/zammad/tmp/unp…

---

_[View the full topic](https://community.zammad.org/t/zammad-web-ui-slow-detailed-documentation-missing-how-to-troubleshoot/10713)._