> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/solution/can-t-create-stacks-request-limit-exceeded.md).

# Can't Create Stacks, 'Request Limit Exceeded'

## Problem

Heat Stack creation fails and errors like the one below are logged in heat.log.

{% tabs %}
{% tab title="Javascript" %}

```javascript
ERROR heat.engine.resource ResourceFailure: resources.avi_pool: Request limit exceeded: You have reached the maximum stacks per tenant, 100. Please delete some stacks.
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - v4.0 and Higher

## Cause

The maximum stacks per tenant limit has been reached.

## Resolution

In PMK, the heat configuration exists on the management plane. Updating *maximum stacks per tenant* will need to be performed by support.

Please open a ticket for assistance with this.

## Additional Information

Below is a summary of the steps taken by support to make this change.

1 - Set `max_stacks_per_tenant= <value>` in /etc/heat/heat.conf

2 - `# systemctl restart openstack-heat-api`

3 - `# systemctl restart openstack-heat-engine`


---

# 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://platform9.com/kb/pmo/solution/can-t-create-stacks-request-limit-exceeded.md?ask=<question>&goal=<user_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.