> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/email-this-issue/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/email-this-issue/faq/email-this-issue-for-jira-cloud-why-is-the-incoming-mail-queue-size-limited.md).

# Why is the Incoming Mail Queue size limited?

The **Succeeded** queue in the Incoming Mail Queue page used to store all successfully processed emails.

However, the overall size of this queue has been increased so dramatically week by week that we needed to make restrictions in order keep the app stable and our database scalable.

From mid-June 2021, the **Succeded** queue will only store successfully processed emails from the past 90 days. This means you’ll be able to search for and review the emails from the past 3 months, but not earlier ones.

This change does not affect the other queues.

In case you have questions, please let us know at <support@metainf.atlassian.net>


---

# 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 dynamically by asking a question.

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

```
GET https://docs.meta-inf.hu/email-this-issue/faq/email-this-issue-for-jira-cloud-why-is-the-incoming-mail-queue-size-limited.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.