If you encounter errors while you are using Anypoint API Community Manager, refer to these explanations and instructions for recovery.

Error When Creating a New Community from a Template

If creating a new community from a template shows the error An unexpected error occurred. Try again or contact your Salesforce administrator for help, compile all Apex classes by opening Setup > Custom Code > Apex Classes and clicking Compile all classes. In a few minutes the page displays the message Compilation Complete: Compilation Successful.

Find more information about compiling Apex classes in the Salesforce help article Manage Apex Classes.

Approved Members Not Created or Emailed

If your Winter '20 Salesforce organization has the member approval workflow active, and approving a member and refreshing the screen removes the member from the list without creating the new user or sending the new user email, troubleshoot by either setting the approver’s language to English or adding the approver’s language.

To set the approver’s language to English, configure the approver user in the SelfRegister component and set the locale to English.

To add the approver’s language:

  1. Open Salesforce setup.

  2. Open company settings.

  3. Open language settings.

  4. Enable the appropriate languages and locales by enabling end-user languages, enabling platform-only languages, or both.

  5. Add the language matching the approver user profile to the list of displayed languages.

Not Authorized or Problem Logging In Error When Saving External Data Source Configuration

If saving the external data source configuration shows one of the errors "Not authorized" or "Problem Logging In - No_Oauth_State: State was not sent back", follow these steps:

  1. Ensure that the connected app domain is the right domain of the Salesforce organization.

  2. Open Salesforce setup.

  3. Open the authentication providers configuration.

  4. Click the name of the Anypoint Platform authentication provider and ensure that it has these settings from the correct connected app in Anypoint Platform:

    1. Ensure that the consumer key and consumer secret match the connected app in Anypoint Platform.

    2. Ensure that the authorize endpoint URL, token endpoint URL, and default scopes are configured as described in Manual Setup.

    3. Ensure that the test-only initialization URL, OAuth-only initialization URL, callback URL, and single logout URL match the correct domain of your Salesforce organization.

    4. Ensure that your connected app in Anypoint Platform has the same domain as your Salesforce organization in its redirect_uri setting, a client ID and client secret that match those in Salesforce, and correct scopes.

To view details of the connected app, examine the UI or make this API call:

curl -X GET '' \
   -H "Content-Type: application/json" \
   -H "authorization: bearer XXXXXXXXX"

This call returns a response like this:

"client_id": "5fafXXXXXXXXXXXXXXXXXXXXXXXX29c9",
"client_secret": "9509XXXXXXXXXXXXXXXXXXXXXXXXC10E",
"client_name": "ACM Integration Client",
"redirect_uris": [
"grant_types": [
"public_keys": [],
"scopes": [
"enabled": true,
"owner_org_id": "f377XXXX-XXXX-XXXX-XXXX-XXXXXXXX9d08",
"as_id": "anypoint"

"YourOrgDomain" is replaced by your organization domain.

Missing Request Access Button

If a published API version is not showing the Request access button:

  1. Ensure that the API version is managed in API Manager.

  2. If it is not, click Import from Exchange.

  3. Ensure that the API version has at least one endpoint defined.

  4. Label the endpoint.

  5. This label displays in your community.

  6. Ensure that at least one of the API version’s endpoints is configured as public in Exchange.

In the community builder, check the audience targeting settings of the API Access Requester Lightning component. To make the API Access Requester appear to all members, ensure that it is not assigned to any audience. To make it appear only to a specific audience, ensure that it is assigned to the correct audience, and verify it by viewing the page while logged in to an account that is a member of this audience.

Broken Images on Documentation Pages

If your community shows a broken image on an API documentation page, and the image displays correctly on the API documentation page in Exchange, follow these steps:

  1. Images uploaded to Exchange with the markdown editor are stored in Exchange.

  2. If the image is stored in Exchange, make the Exchange API version asset public so the image can be rendered in your community.

  3. If the image is stored on a web location outside Exchange, such as S3 or Dropbox:

    1. Open Salesforce setup.

    2. Open your community’s content security policy (CSP) trusted sites list.

    3. Ensure that the list includes the image site domain.

    4. Because some file-sharing services resolve URLs through multiple redirects, ensure that the list includes the domain of the final URL.

To learn if any content in any component or page of the community is blocked by the content security policy:

  1. Open the API Community Manager control panel.

  2. Click Community Builder.

  3. Click Preview.

  4. Open the page that contains the content.

To inspect the URLs the browser loads when rendering a community page, use the browser developer tools.

Console Mocking Service Not Loading

If the console shows a spinning icon and never loads the mocking service:

  1. Open Salesforce setup.

  2. Open the Named Credentials configuration.

  3. Ensure that the Anypoint Platform credentials for the data bridge are configured as described in Manual Setup.

  4. Ensure that the mocking service uses HTTPS.

Unauthorized Endpoint Error

If calling a real endpoint from the console shows an Unauthorized Endpoint error:

  1. Open Salesforce setup.

  2. Open your community’s content security policy (CSP) trusted sites list.

  3. Ensure that the list includes the endpoint site domain.

The console works in the user’s browser and can call only trusted endpoint sites.

Incorrect or Missing Data for One API Version

If a single API version has documentation or console components with incorrect or missing data:

  1. Open the API Community Manager control panel.

  2. Edit the API version.

  3. Click View asset in Exchange.

  4. Ensure that the API version in API Community Manager points to the correct API version in Exchange.

  5. Ensure that the API version in Exchange is published and not in draft mode.

Guest Users Not Seeing Published API Versions

If guest users do not see published API versions that have been set to be visible for everyone:

  1. Open Salesforce setup.

  2. Open the sharing rules.

  3. Ensure that the sharing rule for the object CommunityApi matches your community name exactly, including spacing and letter case.

Refresh the Cache

If changes made to APIs are not visible right after you make them, you can refresh the cache to see them:

  1. Log in to your Salesforce organization.

  2. In Setup, click Platform Cache.

  3. Click the ACMCache partition.

  4. If the caches are in use, then the Clear Cache button is displayed.

  5. Click Clear Cache.

Duplicated External Objects

Validating and synchronizing the external data source generates duplicate external objects that will not be used. Delete these new objects.

Missing Feature Error

If you receive a Missing feaure error when you install Anypoint API Community Manager, ensure that digital experiences (previously known as communities) are enabled in your API Community Manager Salesforce organization.

The error looks similar to this:

1. Lightning Community Themes(communityThemeDefinitions/acm_template.communityThemeDefinition) Missing feature
Installing this package requires the following feature and its associated permissions: Lightning Community Themes
2. Lightning Community Templates(communityTemplateDefinitions/NTO.communityTemplateDefinition) Missing feature
Installing this package requires the following feature and its associated permissions: Lightning Community Templates
3. Navigation Link Sets(navigationMenus/acm_template_Nav0.navigationMenu) Missing feature
Installing this package requires the following feature and its associated permissions: Navigation Link Sets

To fix this error, follow the installation prerequisite steps in the section Set Up a Domain with Enabled Communities.

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub