--- schema_version: "1" id: 2824f4e29fd4b4d218c72a6461d4a2a73339a7fc99ed95b109ce7011966308f2 title: Troubleshooting collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/api-experience-hub/troubleshooting.md canonical_url: https://docs.mulesoft.com/api-experience-hub/troubleshooting source_site: docs.mulesoft.com content_type: documentation content_hash: 16eb84eec460f23c4ba83f4fe7bc3ad5c7388acf7d0269967f26f720de7faa05 description: MuleSoft Documentation Site latest: true --- --- product: API Experience Hub --- # Troubleshooting > For the full documentation index, see: https://docs.mulesoft.com/llms.txt If you encounter errors, refer to the following instructions for recovery. ## Can’t See Images in the Builder Preview That Were Uploaded When Creating the Portal In the Builder preview, you cannot see the images that were uploaded when creating the portal because the shared user isn’t a member of any libraries. To add the shared user as a member of the asset library: 1. Log in to the Salesforce organization as a System Administrator. 2. Click the **App Launcher**, enter **files** in the search box, and select **Files**. 3. Click **Libraries** in the navigation pane. 4. Click **Asset Library** in the list. 5. Click **Manage Members**. The **Manage Library Members** screen opens. 6. In the **Add Members** field, click the down arrow next to the stack icon and select **People**. The **Add Members** field shows the **search people** box. 7. Click in the **search people** box and select **Builder Preview**. 8. In the **Access** field, select **Author**. 9. Click **Add** to allow the Builder Preview user to upload images in the Builder for later use. The **Current Members** section shows the **Builder Preview** member and **Author** access. 10. Close the screen. 11. Confirm that the Builder Preview user can see the library images in the Builder. 12. Reload the page if the images aren’t showing up. ## API Experience Hub Does Not Show on the Anypoint Platform Landing Page If API Experience Hub does not show on the Anypoint Platform landing page, ensure that you’re using the main organization. Contact the MuleSoft administrator to ensure that the entitlement is enabled. ## Error Occurs When Changing the Relax IP Restrictions Option In this release, IP restrictions for the connected app aren’t supported. By default, the IP Restrictions field is set to `Relax IP Restrictions`. If you have Trusted IP Ranges in your organization, they are bypassed by the connected app. To avoid errors, don’t change the **IP Restrictions** field from `Relax IP Restrictions` because it produces errors when creating the portal. ## Error Saving Changes to the Portal When an Object Has Validation Rules Activated An error occurs when saving styling changes to the portal if an object has validation rules applied for standard objects that are created during the Salesforce linking process. You can’t apply validation rules to Salesforce standard objects, such as account and user objects, that are created during the Salesforce linking process. The workaround is to bypass the validation rule for the Salesforce user who performs the linking process. This user must have the System Administrator profile to perform the linking process. > [!NOTE] These instructions pertain to bypassing account object validation rules but can apply to > bypassing custom validation rules of other objects. You can also use an existing permission set > instead of creating a new one. 1. Create a custom permission: 1. From Salesforce, go to **Setup**, enter **custom permissions** in the **Quick Find** box, and select **Custom Permissions**. 2. Click **New** and enter the permission information: - **Label** Enter **Bypass Account Validation Rule**. - **Name** Click the field to populate it with the label name with underscores. - **Description** Enter a description for the permission. 3. Click **Save**. 2. Create a permission set and add the custom permission: 1. From **Setup**, enter **permission sets** in the **Quick Find** box and select **Permission Sets**. 2. Click **New** and enter the permission set information: - **Label** Enter **Bypass Account Validation Rule**. - **Name** Click the field to populate it with the label name with underscores. 3. Click **Save**. 4. Click **Bypass Account Validation Rule** and select **Custom Permissions** from the **Apps** section. 5. From **Available Custom Permissions**, select **Bypass Account Validation**, click **Add**, and then click **Save**. 6. From the **Custom Permissions** list, select **Bypass Account Validation** and **Save**. 7. From **Object Manager**, select **Validation Rules**. 8. Select the object used for the validation rule and click **Edit**. 9. In the **Error Condition Formula** box, enter the following: AND ( NOT($Permission.Bypass\_Account\_Validation), ISBLANK (Website) ) 10. Click **Save**. 3. Assign the permission set to the user performing the linking process: 1. From **Setup**, enter **permission sets** in the **Quick Find** box and select **Permission Sets**. 2. Click **Bypass Account Validation Rule** and click **Manage Assignments**. 3. Click **Add Assignment**, select the user, and then click **Next**. 4. Click **Assign**. 5. Perform the Salesforce linking process using the user with the bypass permission set. ## Error When Installing the Package During the Connection Process If you encounter errors while installing the package during the connecting to Salesforce process, you can review more details about the deployment status: 1. From Salesforce, go to **Setup**. 2. Click **Environments**. 3. Click **Deploy**. 4. Click **Deployment Status**. 5. Review the **Failed** and **Succeeded** sections. ## Linking Process Fails The linking process fails when the user who executes the linking process has the Exchange Contributor role in a business group and this user does not have the System Administrator permission in that same business group. To resolve this issue, add the organization administrator permission to the user who is executing the Salesforce linking in the business group. ## Not Receiving Emails from Salesforce Experience Cloud If you’re not receiving emails from Salesforce Experience Cloud, disable the standard configuration by following these steps: 1. Go to **Setup** > **Deliverability** > **Email Security Compliance**. 2. Deselect **Enable compliance with standard email security mechanisms**. ## Contact MuleSoft Support For professional services customizations, enhancement requests, and other help, contact your MuleSoft Customer Success representative. To report issues or defects in API Experience Hub, submit a support case from [Salesforce Help](https://help.salesforce.com). The MuleSoft support team works closely with the Salesforce support team to coordinate work on any support tickets involving Salesforce technology. Service-level agreements (SLAs) for support are available at the [MuleSoft Product Support and Maintenance Terms](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/mulesoft-cloud-offerings-SLA-forSalesforce-uMSA.pdf) page. ## See Also - [Known Issues](https://help.salesforce.com/s/issues)