Hear from Salesforce leaders on how to create and deploy Agentforce agents.
Contact Us 1-800-596-4880

Troubleshooting Managed Flex Gateway Creation

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 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.

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.