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

# Troubleshooting Managed Omni Gateway Creation

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

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

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

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

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

## Add Managed Omni Gateway Button is Missing

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

Check Your Business Group Managed Omni Gateway Resources

1.  Navigate to **Access Management > Subscription > Runtime Manage Subscription**. If your
    subscription tier doesn’t include **Small Managed Omni Gateways** and **Large Managed Omni
    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
    Omni Gateways** or **Large Managed Omni Gateways**, try redistributing Managed Omni 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 Omni Gateway Button is Disabled

The **Add Managed Omni 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 Omni 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 Omni 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
    Omni Gateway sizes.

To deploy more Managed Omni 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 Omni 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)