---
schema_version: "1"
id: a64fd2d74446090c034d754a597e47e9cd0b88aa62ddfef64efe946ad0e92fdd
title: Troubleshooting Managed Flex Gateway Creation
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/1.9/flex-troubleshoot-managed-creation.md
canonical_url: https://docs.mulesoft.com/gateway/1.9/flex-troubleshoot-managed-creation
source_site: docs.mulesoft.com
content_type: documentation
content_hash: e29e4bd1d9c5f155fef4a529a3a6da38fae370df2629efbce81c1a5a6badfbd5
description: MuleSoft Documentation Site
release: "1.9"
latest: false
---
---
product: Omni Gateway
version: 1.9
---

# Troubleshooting Managed Flex Gateway Creation

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

When creating and deploying a Managed Flex Gateway instance, you might encounter issues. Check these
topics for possible causes and solutions.

- [Add Managed Flex Gateway Button is Missing](#add-button-missing)

- [Add Managed Flex Gateway Button is Disabled](#add-button-disabled)

- [Private Space Not Available](#private-space)

## Add Managed Flex Gateway Button is Missing

The **Add Managed Flex Gateway** button in Runtime Manager might be missing because the selected
business group does not have Managed Flex Gateway resources. Instead you see a "Start protecting
your APIs with Managed Flex Gateways" message and a **Create a Self-Managed Flex Gateway** button.

Check Your Business Group Managed Flex Gateway Resources

1.  Navigate to **Access Management > Subscription > Runtime Manage Subscription**. If your
    subscription tier doesn’t include **Small Managed Flex Gateways** and **Large Managed Flex
    Gateways** resources, contact your MuleSoft representative for more information.

2.  If your business group shows quantity **0/0 in use** or shows **Reassigned** for **Small Managed
    Flex Gateways** or **Large Managed Flex Gateways**, try redistributing Managed Flex Gateway
    resources from one organization or business group to your selected business group. See
    [Redistribute Resources Between Existing Business Groups](https://docs.mulesoft.com/access-management/business-groups#redistribute-resources).

## Add Managed Flex Gateway Button is Disabled

The **Add Managed Flex Gateway** button in Runtime Manager might be disabled due to quota
limitations or insufficient permissions. This issue occurs if you reach the maximum number of
Managed Flex Gateways allowed for all sizes in your organization or if you don’t have the required
_Manage Servers_ and _Read Servers_ Runtime Manager permissions .

Check Managed Flex Gateway quotas for your organization

1.  In Anypoint Platform, go to **Access Management**.

2.  Click **Runtime Manager** in **Subscription** section of the side navigation panel.

3.  Review the Managed Gateway quotas to determine if the quota has been exhausted for all Managed
    Flex Gateway sizes.

To deploy more Managed Flex Gateways, delete existing gateways or upgrade to a subscription plan
with a higher quota.

Verify your permissions

In Access Management, ensure that you have the required _Manage Servers_ and _Read Servers_ Runtime
Manager permissions.

Your Anypoint Platform Admin can add these permissions in Access Management. For more information,
see [Manage Team Permissions](https://docs.mulesoft.com/access-management/configure-teams#manage-team-permissions).

## Private Space Not Available

When creating a new Managed Flex Gateway, if you don’t see the desired Private Space in the
**Deployment Target** list, you might not have the necessary permissions for that Private Space.

Verify the Private Space permissions

1.  In Runtime Manager, access the details of the Private Space you are trying to use.

2.  Navigate to the **Environments** tab.

3.  Confirm that the target organization and environment are within the allowed environments for
    that private space.

If necessary, update the Private Space Environments configuration to include the target organization
and environment:

1.  Modify the Private Space **Environments** configuration to include the target organization and
    environment.

2.  Wait a few minutes for the changes to propagate and be reflected in the **Deployment Target**
    list.

## See Also

- [Known Issues](https://help.salesforce.com/s/issues)